Ok, thanks Mark - makes sense to have this, so I'll just lower it a bit. Cheers, Tim
On Mon, Jun 24, 2013 at 2:31 PM, Mark Miller <markrmil...@gmail.com> wrote: > This is a safety mechanism - you can turn it off by configuring > leaderVoteWait to 0 in solr.xml. > > This is meant to protect the case where you stop a shard or it fails and then > the first node to get started back up has stale data - you don't want it to > just become the leader. So we wait to see everyone we know about in the shard > up to 3 or 5 min by default. Then we know all the shards participate in the > leader election and the leader will end up with all updates it should have. > > You can lower that wait or turn it off with 0. > > - Mark > > On Jun 24, 2013, at 2:15 PM, Timothy Potter <thelabd...@gmail.com> wrote: > >> I'm seeing this message in the logs and it seems weird to me that the >> instance needs to wait to see more replicas. >> >> 2013-06-24 18:12:40,408 [coreLoadExecutor-4-thread-1] INFO >> solr.cloud.ShardLeaderElectionContext - Waiting until we see more >> replicas up: total=2 found=1 timeoutin=139368 >> >> Can someone elaborate on what this means? This messages seems to occur >> after all replicas of a shard fail and I restart one of the nodes. >> Shouldn't it just proceed as if it is the only replica and assume the >> leader role? >> >> This is on 4.2.0 btw. >> >> Cheers, >> Tim >
