Thanks for your response Shawn, very much appreciated. Gil -----Original Message----- From: Shawn Heisey [mailto:s...@elyograg.org] Sent: 16 May 2013 15:59 To: solr-user@lucene.apache.org Subject: RE: Solr 4.3.0: Shard instances using incorrect data directory on machine boot
> The dataDir is set in each solrconfig.xml; each one has been checked > to ensure it points to its corresponding location. The error we see is > that on machine reboot not all of the shards start successfully, and > if the fail was to be a leader the replicas can't take its place > (presumably because the leader incorrect data directory is > inconsistent with their own). Although you can set the dataDir in solrconfig.xml, I would strongly recommend that you don't. If you are using the old-style solr.xml (which has cores and core tags) then set the dataDir in each core tag in solr.xml. This gets read and set before the core is created, so there's less chance of it getting scrambled. The solrconfig is read as part of core creation. If you are using the new style solr.xml (new with 4.3.0) then you'll need absolute dataDir paths, and they need to go in each core.properties file. Due to a bug, relative paths won't work as expected. I need to see if I can make sure the fix makes it into 4.3.1. If moving dataDir out of solrconfig.xml fixes it, then we probably have a bug. Yout Zookeeper problems might be helped by increasing zkClientTimeout. Thanks, Shawn
