Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOC] Add documentation for remote cluster state publication experiemental feature #7347

Closed
1 of 4 tasks
soosinha opened this issue Jun 10, 2024 · 3 comments · Fixed by #7364
Closed
1 of 4 tasks

[DOC] Add documentation for remote cluster state publication experiemental feature #7347

soosinha opened this issue Jun 10, 2024 · 3 comments · Fixed by #7364
Assignees
Labels
3 - Done Issue is done/complete v2.15.0

Comments

@soosinha
Copy link
Member

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

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

@hdhalter hdhalter added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Jun 10, 2024
@hdhalter
Copy link
Contributor

Thanks, @soosinha ! What is the ETA for the doc PR? We have the first release candidate today.

@soosinha
Copy link
Member Author

RC is moved to 6/11. Will be raising PR before that.

@shwetathareja
Copy link
Member

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.

@hdhalter hdhalter added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. labels Jun 11, 2024
@hdhalter hdhalter added 3 - Done Issue is done/complete and removed 2 - In progress Issue/PR: The issue or PR is in progress. labels Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Done Issue is done/complete v2.15.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants