-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
routine: fix that acl stops replicating after regaining leadership (#12295) #12565
Conversation
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.
Thanks for the PR @weichuliu . The code looks great and makes total sense how the original issue occurs and why it fixes it.
Before merging this it would be great to have a test added for the routine Manager to verify the cancleCh behavior and that it allows restarting a task that was already cancelled. I am very confident that this works as described we just want to ensure that we do not break that behavior in the future.
3250451
to
81493b7
Compare
@mkeeler test updated. It's appreciated if you can help to review. |
@mkeeler I have fiexed the review feedbacks. I believe this one is good to go. I'd appreciate if you can follow up with this PR |
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.
Looks wonderful. Thanks for all your work and addressing my feedback.
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/625431. |
🍒✅ Cherry pick of commit 24245ed onto |
🍒✅ Cherry pick of commit 24245ed onto |
🍒✅ Cherry pick of commit 24245ed onto |
Fix the bug that caused acl replication to stop after a node lose-regain leadership.
The investigation is at #12295 (comment)