Skip to content

Backport rolling upgrade multi cluster module to 6.7 branch#38888

Merged
martijnvg merged 4 commits intoelastic:6.7from
martijnvg:backport_rolling_upgrade_multi_cluster_module_to_6_dot_7
Feb 14, 2019
Merged

Backport rolling upgrade multi cluster module to 6.7 branch#38888
martijnvg merged 4 commits intoelastic:6.7from
martijnvg:backport_rolling_upgrade_multi_cluster_module_to_6_dot_7

Conversation

@martijnvg
Copy link
Copy Markdown
Member

@martijnvg martijnvg commented Feb 14, 2019

Some additional changes (see second commit) were required to make ccr rolling upgrade tests work on 6.7 branch.

Backports of #38277 and #38838

* Add rolling upgrade multi cluster test module (elastic#38277)

This test starts 2 clusters, each with 3 nodes.
First the leader cluster is started and tests are run against it and
then the follower cluster is started and tests execute against this two cluster.

Then the follower cluster is upgraded, one node at a time.
After that the leader cluster is upgraded, one node at a time.
Every time a node is upgraded tests are ran while both clusters are online.
(and either leader cluster has mixed node versions or the follower cluster)

This commit only tests CCR index following, but could be used for CCS tests as well.
In particular for CCR, unidirectional index following is tested during a rolling upgrade.
During the test several indices are created and followed in the leader cluster before or
while the follower cluster is being upgraded.

This tests also verifies that attempting to follow an index in the upgraded cluster
from the not upgraded cluster fails. After both clusters are upgraded following the
index that previously failed should succeed.

Relates to elastic#37231 and elastic#38037

* Filter out upgraded version index settings when starting index following (elastic#38838)

The `index.version.upgraded` and `index.version.upgraded_string` are likely
to be different between leader and follower index. In the event that
a follower index gets restored on a upgraded node while the leader index
is still on non-upgraded nodes.

Closes elastic#38835
@martijnvg martijnvg added :Distributed/CCR Issues around the Cross Cluster State Replication features backport v6.7.0 labels Feb 14, 2019
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-distributed

@martijnvg martijnvg merged commit 89b6e08 into elastic:6.7 Feb 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport :Distributed/CCR Issues around the Cross Cluster State Replication features v6.7.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants