-
Notifications
You must be signed in to change notification settings - Fork 289
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
sink(cdc): only check sink stuck for MQ sinks #9742
sink(cdc): only check sink stuck for MQ sinks #9742
Conversation
Signed-off-by: qupeng <qupeng@pingcap.com>
Signed-off-by: qupeng <qupeng@pingcap.com>
/test cdc-integration-mysql-test |
1 similar comment
/test cdc-integration-mysql-test |
Signed-off-by: qupeng <qupeng@pingcap.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CharlesCheung96, sdojjy 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 |
[LGTM Timeline notifier]Timeline:
|
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 |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
What problem does this PR solve?
Issue Number: close #9736 .
Issue Number: close #9695 .
What is changed and how it works?
Other sink categories like
Txn
orCloudStorage
can handles table sink progress callbacks good enough: callbacks won't be lost forever if sink factory fails internally. Otherwise an error will be reported instead, which can cause sink factory re-established correctly.We only have met the callback lose issue for MQ sinks, so only check sink stuck for MQ sink is enough.
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