Rishab Nahata

@saikaranam-amazon updated the req/res for both update/get calls for recommission/decommission

> How are responding regarding failures in executing the call? - ( May be let's track FAILED as a status value. ) Updated the API contract above, including `FAILED` as...

Updated the API structures above

@reta @dblock @elfisher any thoughts on above APIs?

@reta, thanks for taking a look into the RFC. The cluster settings that you mentioned above is more of shard allocation strategy based on the awareness attribute set to the...

@reta, > The seems to be off here, what we need is the awareness attribute (which could be zone), so the APIs could be generalized this way: PUT /_cluster/decommission/awareness/{attribute}/{value} DELETE...

@reta, thanks for the suggestions. I have updated the API path for weights as well. Let me know if this looks good to you?

@reta, thanks for pointing out. Updated above.

@sachinpkale Although, the attribute key value is a node property, but awareness in general is a cluster property. This is how we set the awareness attribute to the cluster -...

Gave the executor more thoughts and realised we can reuse the existing `NodeRemovalClusterStateTaskExecutor` and send a batch of tasks for multiple nodes in a particular zone for it to execute....