Erick, Anshum, Thanks for your replies! Yes, it is replica state that I am looking at, and this the answer I was hoping for.
I am working on a solution that involves moving some replicas to new Solr nodes as they are made available. Before deleting the original replicas backing the shard, I check the replica state to make sure is active for the new replicas. Initially it was working pretty well, but with more recent testing I regularly see the shard go down. The two new replicas go into failed recovery state after the original replicas are deleted, the logs report that a registered leader was not found for the shard. Initially I was concerned that maybe the new shards were not fully synced with the leader, even though I checked for active state. Now I am wondering if the new shards are somehow competing (or somehow reluctant ) to become leader, and thus neither become leader. I plan to test just creating one new replica on a new solr node, checking for state is active, then deleting original replicas, and then creating second new replica. Any thoughts? Matt -----Original Message----- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Wednesday, April 08, 2015 4:13 PM To: solr-user@lucene.apache.org Subject: Re: Clusterstate - state active Matt: In a word, "yes". Depending on the size of the index for that shard, the transition from Down->Recovering->Active may be too fast to catch. If replicating the index takes a while, though, you should at least see the "Recovering" state, during which time there won't be any searches forwarded to that node. Best, Erick On Wed, Apr 8, 2015 at 2:58 PM, Matt Kuiper <matt.kui...@issinc.com> wrote: > Hello, > > When creating a new replica, and the state is recorded as active with in ZK > clusterstate, does that mean that new replica has synched with the leader > replica for the particular shard? > > Thanks, > Matt >
