The first thing I'd do is not send an absolute path. What happens if you just sent -Dsolr.data.dir=data? (no '/')?
We had this discussion a while ago when we were working on auto-discovery, and it turns out that there _are_ legitimate cases in which more than one core/collection can point to the same data dir. You have to very carefully control who writes to the core, and I wouldn't do it unless there was no choice, but some people find it useful. And, in general, I wouldn't mix and match the _core_ admin API with the _collections_ api unless you're very confident in what you are doing. Why isn't just letting the default data.dir location working for you? There are good reasons to make it explicit, mostly just checking that you're not over-thinking the problem. Usually they'll be located in a reasonable place. Best, Erick On Mon, Nov 25, 2013 at 8:12 AM, adfel70 <adfe...@gmail.com> wrote: > I found something strange while trying to create more than one collection > in > SolrCloud: > I am running every instance with -Dsolr.data.dir=/data > If I look at Core Admin section, I can see that I have one core and its > dataDir is set to this fixed location. Problem is, if I create a new > collection, another core is created - but with this fixed index location > again. > I was expecting that the path I sent would serve as the BASE path for all > cores the the node hosts. Current behaviour seems like a bug to me, because > obviously one collection will see data that was not indexed to him. > Is there a way to overcome this? I mean, change the default data dir > location, but still be able to create more than one collection correctly? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Setting-solr-data-dir-for-SolrCloud-instance-tp4103052.html > Sent from the Solr - User mailing list archive at Nabble.com. >
