diff options
| author | Simon Willnauer <simonw@apache.org> | 2017-07-05 22:18:23 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-07-05 22:18:23 +0200 |
| commit | 6e5cc424a81f27ef3a15ab9bb2d8b158f0b6b9a9 (patch) | |
| tree | ad109bb81c0b47f6d9534b6a0bd590c7f9baf2cf /core/src/main/java/org/elasticsearch/rest/action/search/RestSearchAction.java | |
| parent | 26de905f1e53d556087131a26792ff8a57aa45f2 (diff) | |
Switch indices read-only if a node runs out of disk space (#25541)test
Today when we run out of disk all kinds of crazy things can happen
and nodes are becoming hard to maintain once out of disk is hit.
While we try to move shards away if we hit watermarks this might not
be possible in many situations. Based on the discussion in #24299
this change monitors disk utilization and adds a flood-stage watermark
that causes all indices that are allocated on a node hitting the flood-stage
mark to be switched read-only (with the option to be deleted). This allows users to react on the low disk
situation while subsequent write requests will be rejected. Users can switch
individual indices read-write once the situation is sorted out. There is no
automatic read-write switch once the node has enough space. This requires
user interaction.
The flood-stage watermark is set to `95%` utilization by default.
Closes #24299
Diffstat (limited to 'core/src/main/java/org/elasticsearch/rest/action/search/RestSearchAction.java')
0 files changed, 0 insertions, 0 deletions