Hmm…have not seen a report of this before. For the future, FWIW, if you are in a bad state, the best thing to do is stop all the replicas in the shard and then start it again. That way everyone will work together to trade data and determine the best leader.
When you restarted instance 2, instance 1 was already the leader - so 2 just replicates from him. If you stopped the replicas and started them, that is when the best leader is chosen. I'd also encourage you to try out a nightly build if you can - would be good to be sure whatever this problem is is fixed. It would be interesting if you could post the logs of the node that became leader without all of the docs. - Mark On Dec 19, 2012, at 11:08 AM, shreejay <shreej...@gmail.com> wrote: > Hi All, > > I have a solrlcoud instance with 3 shards. Each shard has 2 instance (2 > servers each running a instance of solr) > > Lets say I had Instance1 and instance2 in shard1 … At some point, instance2 > went down due to OOM (out of memory) . instance1 for some reason was not > replicating the data properly and when it became the leader, it had only > around 1% of the data that instance2 had. I restarted instance2, and hoped > that instance1 will replicate from 2, but instead instanace2 replicated from > instance1 . and ended up deleting the original index folder it had. There > were around 2 million documents in that instance. > > Can any one of solrlcoud users give any hints if I can recover this data? > > > > > --Shreejay > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Data-from-deleted-from-Solr-Solr-cloud-tp4028055.html > Sent from the Solr - User mailing list archive at Nabble.com.
