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

Enhancement: add command to set indices to read_only #150

Closed
faxm0dem opened this issue Aug 21, 2014 · 2 comments
Closed

Enhancement: add command to set indices to read_only #150

faxm0dem opened this issue Aug 21, 2014 · 2 comments

Comments

@faxm0dem
Copy link

I'm not sure this has any performance advantages (I'm eager to know if it does), but it might come in handy: add a command to curator to set index.blocks.read_only to true or false.

@untergeek
Copy link
Member

It has no improvement on performance whatever.

Technically speaking, once an index has been optimized to 1 segment per shard, and had bloom filters disabled, there's not really anything else at the software level that will improve performance in any way.

It may be a useful feature for preventing writes. Elasticsearch isn't really even using this feature yet, so this will be on the back-burner for a while.

@faxm0dem
Copy link
Author

You mean, apart from closing the index :-)
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants