TransportClusterStateAction should not (always) sent the full state over the wire #86888
Labels
>bug
:Distributed Coordination/Cluster Coordination
Cluster formation and cluster state publication, including cluster membership and fault detection.
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
Comments
original-brownbear
added
>enhancement
:Distributed Coordination/Cluster Coordination
elasticmachine
added
the
Team:Distributed (Obsolete)
|
Pinging @elastic/es-distributed (Team:Distributed) |
This was referenced Aug 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Currently,
TransportClusterStateActionsends aClusterStateResponsethat contains the full cluster state serialized and uncompressed. This kind of response should never be necessary because the node sending theClusterStateRequestshould already have an up-to-date cluster state available locally.We should be able to find a better scheme for requesting the current cluster state for usages like
RestClusterStateActionthat does not involve serializing a full state over the wire (and as a result of that also results in instantiating a duplicate instance to the node's local cluster state on heap) by reusing the node's local state and only verifying that it is up-to-date with the master node.relates #77466
The text was updated successfully, but these errors were encountered: