On 3/1/2015 9:33 AM, Alexandre Rafalovitch wrote: > On 1 March 2015 at 01:03, Shawn Heisey <apa...@elyograg.org> wrote: >> How exactly does ES split the index files when multiple paths are >> configured? I am very curious about exactly how this works. Google is >> not helping me figure it out. I even grabbed the ES master branch and >> wasn't able to trace how path.data is used after it makes it into the >> environment. > Elasticsearch automatically creates indexes and shards. So, multiple > directories are just used to distribute the shards' indexes among > them. > http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-dir-layout.html > So, when a new shard is created, one of the directories is used either > randomly or usage-based.
So specifying multiple paths for path.data in ES is NOT a way to split a single Lucene index across multiple directories? That was the implication that I took from the OP's question. If path.data is a more general config that is used to contain the data for all indexes in the application and not something that gets specified per index, then there is no need for Solr to emulate it, because Solr can already specify a completely different data directory for each core/shard. Thanks, Shawn
