You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
totrue
orfalse
.The text was updated successfully, but these errors were encountered: