I'm new to Elasticsearch. I was wondering if there was a way for the index
and documents to live on a read-only filesystem; so far I've read about
setting index.blocks.read_only to true, but it seems that Elasticsearch
still needs write access.
I tested that by naively doing
sudo chmod -R a-w /var/lib/elasticsearch
sudo service elasticsearch restart
after setting index.blocks.read_only to true, but the service failed to
start, as I feared but also expected
Or what about splitting the index over two filesystems, where the volatile
part lives on a writable filesystem and the static part on a read-only
filesystem? I don't know much about Elasticsearch's internals yet, but I'm
assuming that if you are not redistributing your shards over multiple
running instances, and not having to reindex anything because you're not
modifying any documents, then most of the index and all the documents
should be able to be static?
I read this message  on this list, but it seems that is more about
restricting access to Elasticsearch rather than keeping the index on a
(I'm running Elasticsearch on an Ubuntu 13.04 system, if that makes any
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.