Those are paths? /data/solr off the root? When using the collections api, you really don't want to set an absolute data dir - it should be relative, I'd just take the default. Then, even though many shards shard that solrconfig and data dir, they will all find a nice home relative to the instance dir. If you don't do this, you won't be able to over shard, and things get tricky fast.
- Mark On Mar 29, 2013, at 2:45 PM, Chris R <corg...@gmail.com> wrote: > So, upgraded to 4.2 this morning. I had gotten to the point where I okay > with the collection creation process in 4.1 using the API vice the solr.xml > file in 4.0, but now 4.2 doesn't seem to want to create the instanceDir? > > e.g. the Dashboard reports the following when my solr.data.dir is set to > /data/solr in the solrconfig.xml. However, the instance dirs aren't > created, yet the index and tlog dirs are > > Instance /data/solr/collection1_shard1_replica1 > Data /data/solr > Index /data/solr/index > > - > > > Chris > > On Thu, Mar 28, 2013 at 7:48 PM, Mark Miller <markrmil...@gmail.com> wrote: > >> >> On Mar 28, 2013, at 7:30 PM, Shawn Heisey <s...@elyograg.org> wrote: >> >>> Can't you leave numShards out completely, then include a numShards >> parameter on a collection api CREATE url, possibly giving a different >> numShards to each collection? >>> >>> Thanks, >>> Shawn >>> >> >> Yes - that's why I say the collections API is the way forward - it has >> none of these limitations. The limitations are all around pre-configuring >> everything in solr.xml and not using the collections API. >> >> - Mark
