Skip to content
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

Clear read only flag on indexes once disk space is available #34510

Closed
dmitrymurashenkov opened this issue Oct 16, 2018 · 2 comments
Closed

Clear read only flag on indexes once disk space is available #34510

dmitrymurashenkov opened this issue Oct 16, 2018 · 2 comments
Labels
:Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement help wanted adoptme

Comments

@dmitrymurashenkov
Copy link

Currently elastic makes indexes read only if disk filled over 95% by setting flag on index:

index.blocks.read_only_allow_delete: true

Once we clean up the disk and space is available again - flag has to be cleared manually. For example like this:
curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'

It would be nice to have some automatic way to handle this situation.

Seems it would require some additional flag to tell us that this index was locked because of the low disk space and not explicitly by user.

@vladimirdolzhenko vladimirdolzhenko added >enhancement :Distributed/Engine Anything around managing Lucene and the Translog in an open shard. labels Oct 16, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@ywelsch ywelsch added :Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) and removed :Distributed/Engine Anything around managing Lucene and the Translog in an open shard. labels Mar 15, 2019
@DaveCTurner DaveCTurner added the help wanted adoptme label Mar 18, 2019
@DaveCTurner
Copy link
Contributor

DaveCTurner commented Mar 18, 2019

Thanks for opening this issue @dmitrymurashenkov. The same idea was more recently suggested in #39334 and we discussed that as a team and agreed it was a good idea. There's little point in having both issues open, and although this one was opened first we added our collective thoughts in
#39334 (comment). Therefore I am closing this as a duplicate. Please continue any discussion of this idea over on #39334.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement help wanted adoptme
Projects
None yet
Development

No branches or pull requests

5 participants