-
Notifications
You must be signed in to change notification settings - Fork 36
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
Graceful replication shutdown #645
Conversation
LGTM 👍 A couple of questions; Do we stop publishers to leader somewhere? Or can this keep going "forever" if you keep publishing? Maybe that is done by the server earlier when initiating shutdown? Should there be some kind of timeout on the sync? I don't see anything like that in this code. Maybe we should let that be handled outside of LavinMQ though |
Replication is closed last, so vhost should have closed all client connections before (and shovels/federations).
Yes, timeout or similar will probably be part of #547. |
Let followers sync up when shutting down a replicating server. Co-Authored-By: Jon Börjesson <[email protected]>
a0b1e5a
to
11c3174
Compare
This reverts commit 2759ead.
This reverts commit 2759ead.
This reverts commit 2759ead.
This reverts commit 2759ead.
This reverts commit 2759ead.
This reverts commit 2759ead.
This reverts commit 2759ead.
This reverts commit 2759ead.
This reverts commit 2759ead.
Let followers sync up when shutting down a replicating server. Co-authored-by: Jon Börjesson <[email protected]>
WHAT is this pull request doing?
Wait for followers to be in sync before closing server.
HOW can this pull request be tested?
run specs for #close