Skip to content

Commit c6666fc

Browse files
committed
rolling upgrade should use a replica to prevent relocations while running a scroll
A scroll holds a reference to the shard store. If the cluster is moving shards around that reference can prevent a shard from relocating back to node it used to be on, causing test failures. Closes #31827
1 parent 4d83a0d commit c6666fc

File tree

1 file changed

+4
-1
lines changed
  • x-pack/qa/rolling-upgrade/src/test/resources/rest-api-spec/test/mixed_cluster

1 file changed

+4
-1
lines changed

x-pack/qa/rolling-upgrade/src/test/resources/rest-api-spec/test/mixed_cluster/10_basic.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,10 @@
66
wait_for_active_shards: all
77
body:
88
settings:
9-
number_of_replicas: 0
9+
# we use 1 replica to make sure we don't have shards relocating. Relocating a shard with
10+
# a scroll on it prevents shards from moving back into a where a scroll is running (it holds the shard lock)
11+
# see https://github.com/elastic/elasticsearch/issues/31827
12+
number_of_replicas: 1
1013
index.routing.allocation.include.upgraded: true
1114

1215
- do:

0 commit comments

Comments
 (0)