Dianna Hohensee comments

Results 4 comments of


                                            Dianna Hohensee

PUT /_snapshot/{repository} with invalid repository configuration returns an error response but still successfully changes the config

The request also returned a 500 error, so it seems like that wasn't sufficient to stop the config from being set. Would we want to confirm the config works before...

PUT /_snapshot/{repository} with invalid repository configuration returns an error response but still successfully changes the config

> but that'd mean creating a temporary repository instance on each node just for the verification Is there anything stopping us from only doing an initial verification on the node...

An interrupted node-left operation can leave a node (even if it rejoins later) on a list of faultyNodes that do not receive cluster state updates until a LagDetector timeout

Hmm. You're right, there could be multiple node-join requests sent and received out-of-order, don't want to run node-left every time. I was hoping to avoid directly checking for the node...

Make max shard limit variable public, and clearer variable names

@elasticmachine test this please