Skip to content

Conversation

ywangd
Copy link
Member

@ywangd ywangd commented Jul 31, 2025

Backport

This will backport the following commits from main to 9.1:

Questions ?

Please refer to the Backport tool documentation

…2157)

This is the same failure as observed in elastic#129644 for which the original
fix elastic#129680 did not really work. It did not work because the the
ordering of checks. The shutdown marker is removed after the cluster
passes ready check so that new shards can be allocated. But the cluster
cannot pass the ready check before the shards are allocated. Hence the
circular dependency. In hindsight, there is no need to put shutdown
record for all nodes. It is only needed on the node that upgrades the
last to prevent snapshot from completion during the upgrade process.
This PR does that which ensures there are always 2 nodes for hosting new
shards.

Resolves: elastic#132135 Resolves: elastic#132136 Resolves: elastic#132137
(cherry picked from commit f39ccb5)

# Conflicts:
#	muted-tests.yml
@ywangd ywangd added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Jul 31, 2025
@elasticsearchmachine elasticsearchmachine merged commit 04cbfc0 into elastic:9.1 Jul 31, 2025
34 checks passed
@ywangd ywangd deleted the backport/9.1/pr-132157 branch July 31, 2025 06:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v9.1.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants