[skip ci] Optional delay in make restart-cluster
#15029
Merged
+4
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`make restart-cluster` allows simple rolling restart/upgrade testing. `make restart-cluster RESTART_DELAY=N` adds an option to force a delay from when a node goes down, till it start up again. This is useful in some tests scenarios, such as: 1. forcing the cluster to work longer in a mixed-version configuration 2. forcing the stopped member to fall behind in terms of replication to trigger a more demanding catch-up
michaelklishin
approved these changes
Nov 29, 2025
michaelklishin
added a commit
that referenced
this pull request
Nov 30, 2025
[skip ci] Optional delay in `make restart-cluster` (backport #15029)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
make restart-clusterallows simple rolling restart/upgrade testing.make restart-cluster RESTART_DELAY=Nadds an option to force a delay from when a node goes down, till it start up again. This is useful in some tests scenarios, such as:forcing the cluster to work longer in a mixed-version configuration
forcing the stopped member to fall behind in terms of replication to trigger a more demanding catch-up