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

changefeed: Fix changefeed fails immediately after being created successfully. (#2115) #2236

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #2115

What problem does this PR solve?

Fix changefeed fails immediately after being created successfully.

Close #2113

What is changed and how it works?

Check List

Tests

  • Manual test (add detailed scripts or steps below)
  1. create three changefeeds(test1,test2,test3) and stop test3 until it blocks the gcSafepoint advance.
$ curl http://127.0.0.1:8300/api/v1/changefeeds?state=stopped
[
 {
  "id": "test3",
  "state": "stopped",
  "checkpoint-tso": 425790752871415809,
  "checkpoint-time": "2021-06-21 16:07:00.707",
  "error": null
 }

mysql> select * from mysql.tidb where VARIABLE_NAME="tikv_gc_safe_point";
+--------------------+-------------------------+--------------------------------------------------------------+
| VARIABLE_NAME      | VARIABLE_VALUE          | COMMENT                                                      |
+--------------------+-------------------------+--------------------------------------------------------------+
| tikv_gc_safe_point | 20210621-16:07:00 +0800 | All versions after safe point can be accessed. (DO NOT EDIT) |
+--------------------+-------------------------+--------------------------------------------------------------+
1 row in set (0.01 sec)
  1. create changefeed test13 and let: --start-ts = ${test3's checkpointTs}.
$ ./bin/cdc cli changefeed create --sink-uri="blackhole://" --start-ts 425790752871415809 --changefeed-id="test13"
Create changefeed successfully!
ID: test13
  1. test13 works well.
 $ curl http://127.0.0.1:8300/api/v1/changefeeds?state=normal
[
 {
  "id": "test13",
  "state": "normal",
  "checkpoint-tso": 425791107210674177,
  "checkpoint-time": "2021-06-21 16:29:32.404",
  "error": null
 },

Code changes

  • None

Side effects

  • None

Related changes

  • Need to cherry-pick to the release branch

Release note

  • No release note

@ti-chi-bot
Copy link
Member Author

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added do-not-merge/cherry-pick-not-approved status/ptal Could you please take a look? size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/cherry-pick-for-release-4.0 This PR is cherry-picked to release-4.0 from a source PR. labels Jul 7, 2021
@ti-chi-bot ti-chi-bot requested review from zier-one and lonng July 7, 2021 08:32
@ti-chi-bot
Copy link
Member Author

@asddongmen: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot ti-chi-bot removed the status/can-merge Indicates a PR has been approved by a committer. label Jul 8, 2021
@lonng lonng added this to the v4.0.14 milestone Jul 12, 2021
@lonng lonng added cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels Jul 12, 2021
@overvenus
Copy link
Member

/merge

@ti-chi-bot
Copy link
Member Author

This pull request has been accepted and is ready to merge.

Commit hash: 723051d

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jul 12, 2021
@ti-chi-bot
Copy link
Member Author

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@codecov-commenter
Copy link

Codecov Report

Merging #2236 (b49f0de) into release-4.0 (753073a) will increase coverage by 0.5651%.
The diff coverage is 59.6037%.

@@                 Coverage Diff                 @@
##           release-4.0      #2236        +/-   ##
===================================================
+ Coverage      53.7661%   54.3313%   +0.5651%     
===================================================
  Files              153        166        +13     
  Lines            15958      19867      +3909     
===================================================
+ Hits              8580      10794      +2214     
- Misses            6475       8038      +1563     
- Partials           903       1035       +132     

@ti-chi-bot ti-chi-bot merged commit a5210c0 into pingcap:release-4.0 Jul 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-approved Cherry pick PR approved by release team. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. status/ptal Could you please take a look? type/cherry-pick-for-release-4.0 This PR is cherry-picked to release-4.0 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants