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

[Remote State] Make Remote publication a dynamic setting #15852

Open
shiv0408 opened this issue Sep 9, 2024 · 0 comments · May be fixed by #15937
Open

[Remote State] Make Remote publication a dynamic setting #15852

shiv0408 opened this issue Sep 9, 2024 · 0 comments · May be fixed by #15937
Labels
ClusterManager:RemoteState enhancement Enhancement or improvement to existing feature or request

Comments

@shiv0408
Copy link
Member

shiv0408 commented Sep 9, 2024

Is your feature request related to a problem? Please describe

Currently, if we want to enable or disable the remote publication. We would need to restart cluster manager nodes after modifying the setting in the opensearch.yml file. This makes changing the publication channel very cumbersome.

Describe the solution you'd like

We want to have a dynamic setting, where we can disable or enable the remote publication by just doing a put setting API call. Remote State can be continued to be uploaded from the active master node.
Here, only the active master node will make the decision if we need to make the publication using remote channel or transport channel. Other follower nodes will be dumb followers, just relying on the kind of call that has been received on these nodes. If they receive the REMOTE_PUBLISH_REQUEST, they will use the remote store to download the state and apply that. Or, if the state is received on the transport channel, it will just apply that state.

Related component

Cluster Manager

Describe alternatives you've considered

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ClusterManager:RemoteState enhancement Enhancement or improvement to existing feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant