Skip to content

Conversation

@nielsbauman
Copy link
Contributor

This action solely needs the cluster state, it can run on any node. Since this action is invoked across clusters, we need to be able to (de)serialize requests and responses. We introduce a new RemoteClusterStateRequest that wraps the existing ClusterStateRequest and implements (de)serialization.

This action solely needs the cluster state, it can run on any node.
Since this action is invoked across clusters, we need to be able to
(de)serialize requests and responses. We introduce a new
`RemoteClusterStateRequest` that wraps the existing
`ClusterStateRequest` and implements (de)serialization.
@nielsbauman nielsbauman requested a review from DaveCTurner June 23, 2025 16:50
@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v9.1.0 labels Jun 23, 2025
@nielsbauman nielsbauman added :Data Management/Indices APIs APIs to create and manage indices and templates :Distributed Coordination/Distributed A catch all label for anything in the Distributed Coordination area. Please avoid if you can. and removed needs:triage Requires assignment of a team area label labels Jun 23, 2025
@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team Team:Distributed Coordination Meta label for Distributed Coordination team labels Jun 23, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

@elasticsearchmachine
Copy link
Collaborator

Hi @nielsbauman, I've created a changelog YAML for you.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a couple of comments

@nielsbauman nielsbauman removed the :Data Management/Indices APIs APIs to create and manage indices and templates label Jul 3, 2025
@elasticsearchmachine elasticsearchmachine removed the Team:Data Management Meta label for data/management team label Jul 3, 2025
Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nielsbauman nielsbauman enabled auto-merge (squash) July 8, 2025 09:11
@nielsbauman nielsbauman merged commit ecbc360 into elastic:main Jul 8, 2025
34 checks passed
@nielsbauman nielsbauman deleted the local-cluster-state branch July 8, 2025 12:21
ywangd added a commit to ywangd/elasticsearch that referenced this pull request Jul 14, 2025
The shard started may not be visible on the master node if the wait is
on a data node. In that case, the DiskThreshold monitor may use stale
cluster state for releasing read-only blocks. This PR fixes it by
waiting on the master node, which is the behaviour before elastic#129872.

Resolves: elastic#131146
elasticsearchmachine pushed a commit that referenced this pull request Jul 15, 2025
The shard started may not be visible on the master node if the wait is
on a data node. In that case, the DiskThreshold monitor may use stale
cluster state for releasing read-only blocks. This PR fixes it by
waiting on the master node, which is the behaviour before #129872.

Resolves: #131146
mridula-s109 pushed a commit to mridula-s109/elasticsearch that referenced this pull request Jul 17, 2025
The shard started may not be visible on the master node if the wait is
on a data node. In that case, the DiskThreshold monitor may use stale
cluster state for releasing read-only blocks. This PR fixes it by
waiting on the master node, which is the behaviour before elastic#129872.

Resolves: elastic#131146
mridula-s109 pushed a commit to mridula-s109/elasticsearch that referenced this pull request Jul 17, 2025
The shard started may not be visible on the master node if the wait is
on a data node. In that case, the DiskThreshold monitor may use stale
cluster state for releasing read-only blocks. This PR fixes it by
waiting on the master node, which is the behaviour before elastic#129872.

Resolves: elastic#131146
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed Coordination/Distributed A catch all label for anything in the Distributed Coordination area. Please avoid if you can. >enhancement serverless-linked Added by automation, don't add manually Team:Distributed Coordination Meta label for Distributed Coordination team v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants