dm: reset optimistic sharding group keeper when syncer resume (#9707) #9719
Conversation
ti-chi-bot
bot
added
do-not-merge/cherry-pick-not-approved
release-note
ti-chi-bot
added
lgtm
size/S
|
This cherry pick PR is for a release branch and has not yet been approved by release team. To merge this cherry pick, it must first be approved by the collaborators. AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review. 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 kubernetes/test-infra repository. |
ti-chi-bot
added
the
type/cherry-pick-for-release-6.5
|
@Benjamin2037: adding LGTM is restricted to approvers and reviewers in OWNERS files. 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 kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Benjamin2037, GMHDBJD 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 |
ti-chi-bot
added
the
cherry-pick-approved
This is an automated cherry-pick of #9707
What problem does this PR solve?
Issue Number: close #9588
What is changed and how it works?
Root Cause
when syncer resume, the remain sharding group keeper infos will block replication if we not reset it
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