You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tell us about your request. Provide a summary of the request and all versions that are affected.
Remote cluster state publication is being released as an experimental feature. When this is enabled, the details of the remote cluster state uploaded in blob store will be sent over the transport layer to follower nodes instead of sending the cluster state object.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
Meta issue: opensearch-project/OpenSearch#13683
The text was updated successfully, but these errors were encountered:
Cluster state publication via remote - When it is enabled, the updated cluster state during any updates like creation of an index, put mappings etc. will be published via remote store i.e. cluster manager will provide the remote location and nodes will download the cluster state directly from remote location. As the cluster state grows over time and there are large no. of nodes in the cluster, publishing the state over local transport tends to add lot of overhead in terms of cpu, memory and transport threadpool. This will reduce the overhead on cluster manager node to publish the updated cluster state via remote store to every other node in the cluster instead of local transport.
What do you want to do?
Tell us about your request. Provide a summary of the request and all versions that are affected.
Remote cluster state publication is being released as an experimental feature. When this is enabled, the details of the remote cluster state uploaded in blob store will be sent over the transport layer to follower nodes instead of sending the cluster state object.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
Meta issue: opensearch-project/OpenSearch#13683
The text was updated successfully, but these errors were encountered: