-
Notifications
You must be signed in to change notification settings - Fork 286
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
owner, redo(ticdc): decouple globalResolvedTs and globalBarrierTs #8964
owner, redo(ticdc): decouple globalResolvedTs and globalBarrierTs #8964
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Skipping CI for Draft Pull Request. |
e56cf08
to
2f601cd
Compare
/test all |
/test cdc-integration-mysql-test |
2f601cd
to
30263a8
Compare
/test all |
1 similar comment
/test all |
2e92cdf
to
a222ac2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you add some comments in detail about the issue
@@ -443,8 +443,8 @@ func (c *changefeed) tick(ctx cdcContext.Context, captures map[model.CaptureID]* | |||
} | |||
}) | |||
|
|||
c.updateStatus(newCheckpointTs, newResolvedTs, minTableBarrierTs) | |||
c.updateMetrics(currentTs, newCheckpointTs, metricsResolvedTs) | |||
c.updateStatus(newCheckpointTs, newResolvedTs, barrier.minDDLBarrierTs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which one is the globalBarrierTs now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updateStatus
only update status in etcd, however globalBarrierTs is updated by p2p, ref: https://github.com/pingcap/tiflow/pull/8964/files#diff-953746562776cf8aa41cd4a971df8c546649d2721ae787607aed2069f3b44eb0R353-R354
updated, PTAL: #8963 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 0f9f299
|
@CharlesCheung96: 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. |
/test all |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created to branch |
What problem does this PR solve?
Issue Number: close #8963
What is changed and how it works?
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note