-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Rolling upgrade tests with 3 nodes #25336
Copy link
Copy link
Labels
:Core/Infra/CoreCore issues without another labelCore issues without another label>testIssues or PRs that are addressing/adding testsIssues or PRs that are addressing/adding tests
Description
TL;DR: I'm adding a BWC layer in #24841 that will only be triggered in a mixed-version cluster with at least 3 nodes and an index with at least 3 shard copies (i.e. index.number_of_replicas > 1). Q: Should we change our existing qa/rolling-upgrade tests to run with 3 nodes?
Details: When a primary fails and a replica is promoted to primary, the new primary will trigger a primary-replica resync, making sure that all the replicas are realigned with the new primary. This is a transport action that will only go into 6.0, not into 5.x. As such I added a BWC layer to the transport action that it will not send these resync requests to 5.6 nodes (i.e. replicas on 5.6 nodes won't be realigned with the new 6.0 primary, same as we do today in < 6.0).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Core/Infra/CoreCore issues without another labelCore issues without another label>testIssues or PRs that are addressing/adding testsIssues or PRs that are addressing/adding tests
Type
Fields
Give feedbackNo fields configured for issues without a type.