Skip to content
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

[7.x] Add target_node_name for REPLACE shutdown type (#77151) #77278

Merged
merged 5 commits into from
Sep 7, 2021

Conversation

gwbrown
Copy link
Contributor

@gwbrown gwbrown commented Sep 3, 2021

Backports the following commits to 7.x:

This commit extends the `REPLACE` shutdown type to support a new
`target_node_name` field, which will control the node used to replace
the one that is to shut down. However, only the data layer is present as
of this PR.

Also adjusts the serialization/deserialization for the REPLACE type to
handle mixed-version clusters.
@gwbrown gwbrown added auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport labels Sep 3, 2021
@gwbrown gwbrown removed the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Sep 3, 2021
This commit fixes the randomization in MlNodeShutdownIT to ensure that
the required values for the selected shutdown type are all present.
Co-authored-by: David Roberts <dave.roberts@elastic.co>
@gwbrown
Copy link
Contributor Author

gwbrown commented Sep 7, 2021

@elasticmachine update branch

@gwbrown gwbrown merged commit f586405 into elastic:7.x Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants