Hi Ranjith, Here are a few things to note about shard split: 1. The command auto-retries. Also, if there's something that went wrong during a split, you should wait for it to complete. 2. In case of a failure, the parent shard is supposed to be intact and the new sub-shards wouldn't replace the parent shard. 3. If you tried using 4.3.*, the commit isn't called and so the documents wouldn't be visible on the subshards unless you call an explicit commit. Having said that, I'd highly recommend you not to use 4.3 for trying to shard splitting.
Can you explain further by what you mean by "documents are getting lost"? AFAIR, the code is supposed to handle failure midway through the shard split call, including dead leader/overseer. On Wed, Aug 7, 2013 at 3:07 PM, Ranjith Venkatesan <ranjit...@zohocorp.com>wrote: > Hi Erick, > > I have a question. Suppose if any error occurred during shard split , is > there any approach to revert back the split action? . This is seriously > breaking my head. For me documents are getting lost when any of the node > for > that shard is dead when split shard is in progress. > > Thanks > > Ranjith > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Split-Shard-Document-loss-and-down-time-tp4082002p4082973.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Anshum Gupta http://www.anshumgupta.net
