SYSTEM STOP SWARM MODE command for graceful shutdown swarm node merge attempt v2 #1014
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
SYSTEM STOP SWARM MODE command for graceful shutdown swarm node
Documentation entry for user-facing changes
Solved #759
New command
SYSTEM STOP SWARM MODE.Scenario:
We want to scale down swarm cluster. On node which we want to shutdown we call
SYSTEM STOP SWARM MODE, after that node stops to accept new distributed commands. It can still processed objects which is started processed beforeSYSTEM STOP SWARM MODE. When all that objects successfully processed, we can kill that node without any errors or lost data in responses on initiator.After
SYSTEM STOP SWARM MODEon swarm node:On initiator node:
skip_unavailable_shards=trueunexpected closing of socket is legal if no data packets were accepted before. This allow to shutdown non-autodiscovery node too.Exclude tests: