Skip to content

Conversation

mosche
Copy link
Contributor

@mosche mosche commented Sep 22, 2025

Backport

This will backport the following commits from main to 9.1:

Questions ?

Please refer to the Backport tool documentation

…#134368)

This was failing very very rarely due to unfortunate timing conditions.

Cluster state changes are applied to all nodes prior to being published
on the master node itself. However, the cluster state listener was
previously attached to the data node, allowing for a very short time
window where the state update wasn't visible on the master node itself
when checking in `assertClusterStateSaveOK`.

This changes the test to attach the listener to the master node itself
preventing above condition. I was initially worried it might be attached
too late in cases, but I couldn't reproduce any more issues this way.

> According to the dashboard, this started to fail on Monday (13/07). It
definitely does not look like a test failure, so I'm assigning a medium
priority, which we could raise if we discover this is a new bug.

I couldn't find any related commit that might have caused this. Still
wondering why this started failing around that time 🤔

Fixes elastic#131210

(cherry picked from commit a29392c)

# Conflicts:
#	muted-tests.yml
@mosche mosche added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Sep 22, 2025
@elasticsearchmachine elasticsearchmachine merged commit a4b1cd5 into elastic:9.1 Sep 22, 2025
35 checks passed
@mosche mosche deleted the backport/9.1/pr-134368 branch September 22, 2025 15:02
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.5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants