-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
high disk watermark more than flood stage disk watermark #8
Comments
Ugh ok. I guess this repo will have to handle setting the flood stage disk watermark as well, and instruct people to ensure the two values are set appropriately. |
Are those settings not currently coming from this repo? |
They are configurable, so any terraform project using this repository can set them. |
I had a look into this and unfortunately, the curl -XPUT \
-H 'Content-Type: application/json' \
-d '
{
"persistent": {
"cluster.routing.allocation.disk.watermark.flood_stage": "50%"
}
}' \
'localhost:9200/_cluster/settings?pretty=true' {
"error" : {
"root_cause" : [
{
"type" : "illegal_argument_exception",
"reason" : "persistent setting [cluster.routing.allocation.disk.watermark.flood_stage], not dynamically updateable"
}
],
"type" : "illegal_argument_exception",
"reason" : "persistent setting [cluster.routing.allocation.disk.watermark.flood_stage], not dynamically updateable"
},
"status" : 400
} |
saw this in the ES6 logs:
The text was updated successfully, but these errors were encountered: