-
Notifications
You must be signed in to change notification settings - Fork 0
Handle some scenarios that we need to cancel ASM #57
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
Conversation
|
@ShooterIT As you are working on this, I think we should also consider cancelling on FAILOVER. Master will pause writes during failover and if we complete migration during this write pause, source side will try to trim keys which will also try to write to repl log. It eventually triggers an assert here: |
|
thanks, i missed that, you mean |
|
yes, CLUSTER FAILOVER command |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## cluster-asm #57 +/- ##
==============================================
Coverage ? 69.69%
==============================================
Files ? 125
Lines ? 73876
Branches ? 0
==============================================
Hits ? 51487
Misses ? 22389
Partials ? 0
🚀 New features to boost your workflow:
|
- CLUSTER FORGET command - CLUSTER ADDSLOTS/DELSLOTS command - CLUSTER SETSLOTS command - CLUSTER FAILOVER command - CLIENT PAUSE command - server shutdown (SHUTDOWN command or kill)
- CLUSTER FORGET command - CLUSTER ADDSLOTS/DELSLOTS command - CLUSTER SETSLOTS command - CLUSTER FAILOVER command - CLIENT PAUSE command - server shutdown (SHUTDOWN command or kill)
Uh oh!
There was an error while loading. Please reload this page.