Cluster down after typo on search backpressure cluster setting

OpenSearch
2

@spapadop This setting could be reverted by configuring a null value. However, as you’ve noticed, nodes are looped in the reported error which prevents any cluster settings modifications.

OpenSearch node applies the settings in the following order:

  1. Transistent setting
  2. Persistent setting
  3. opensearch.yml
  4. default settings

So if there was a chance of setting the reported cluster setting in the opensearch.yml, it wouldn’t override the persistent setting.

Take a look at this reported bug OpenSearch handling for invalid setting value instead of corrupting the state · Issue #7598 · opensearch-project/OpenSearch · GitHub

There is also a method described which allows to remove an unwanted setting. However, please be aware that the tool reports itself as A CLI tool to do unsafe cluster and index manipulations on current node