Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v6.5.6] Documented resuming changefeed from Failed state (#15555) #15875

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #15555

What is changed, added or deleted? (Required)

From the Failed state the changefeed may be resumed (within the gc-ttl duration). For example, if a downstream issue is encountered for longer than 30 minutes the changefeed transitions to the Failure state. If that downstream issue is resolved within a few hours (less than the default 24 hour gc-ttl) the user may successfully resume the changefeed. This was not documented in the current overview.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v7.6 (TiDB 7.6 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.4 (TiDB 7.4 versions)
  • v7.3 (TiDB 7.3 versions)
  • v7.1 (TiDB 7.1 versions)
  • v7.0 (TiDB 7.0 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot added contribution This PR is from a community contributor. lgtm size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-6.5 This PR is cherry-picked to release-6.5 from a source PR. labels Dec 26, 2023
ticdc/ticdc-changefeed-overview.md Outdated Show resolved Hide resolved
ticdc/ticdc-changefeed-overview.md Outdated Show resolved Hide resolved
@qiancai
Copy link
Collaborator

qiancai commented Dec 27, 2023

/approve

Copy link

ti-chi-bot bot commented Dec 27, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Dec 27, 2023
@qiancai qiancai added the needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. label Dec 27, 2023
@ti-chi-bot ti-chi-bot bot merged commit 9d2413b into pingcap:release-6.5 Dec 27, 2023
9 checks passed
@ti-chi-bot
Copy link
Member Author

In response to a cherrypick label: new pull request created to branch release-7.1: #15895.

ti-chi-bot added a commit to ti-chi-bot/docs that referenced this pull request Dec 27, 2023
@qiancai qiancai changed the title Documented resuming changefeed from Failed state (#15555) [v6.5.6] Documented resuming changefeed from Failed state (#15555) Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved contribution This PR is from a community contributor. lgtm needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-6.5 This PR is cherry-picked to release-6.5 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants