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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: