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
Currently, a local healthcheck request on local decommissioned node would return cluster health response from its local cluster state saying cluster manager not discovered. But currently transport calls on a local decommissioned node won't be able to identify if it is decommissioned or not. There might be a use case to get that info from a local decommissioned node directly on local transport calls
Describe the solution you'd like
We can add a param in cluster health call to identify a node is decommissioned or not on a local node
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
imRishN
changed the title
[RFC] Show decommission status in Cluster Health API
[Zone Decommission] [RFC] Show decommission status in Cluster Health API
Sep 15, 2022
imRishN
changed the title
[Zone Decommission] [RFC] Show decommission status in Cluster Health API
[Zone Decommission] Cluster Health local API should throw decommissioned exception for local node if decommissioned
Jan 25, 2023
Currently, a local healthcheck request on local decommissioned node would return cluster health response from its local cluster state saying cluster manager not discovered. But currently transport calls on a local decommissioned node won't be able to identify if it is decommissioned or not. There might be a use case to get that info from a local decommissioned node directly on local transport calls
Describe the solution you'd like
We can add a param in cluster health call to identify a node is decommissioned or not on a local node
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: