By default, on cluster startup, we wait until we see all the replicas for a shard come up. This is for safety. You may have introduced an old shard with old data or a new shard with no data, and you don't want something like that becoming the leader.
If you don't want to do this wait, it's configurable. In solr.xml change the <cores attribute leaderVoteWait to n milliseconds or 0. It defaults to 180000 (3 minutes). - Mark On Feb 12, 2013, at 8:31 AM, adm1n <evgeni.evg...@gmail.com> wrote: > Hi all, > the first question: > is there a way to reduce timeout when sold shard comes up? it looks in log > file as follows: > > Feb 12, 2013 1:19:08 PM org.apache.solr.cloud.ShardLeaderElectionContext > waitForReplicasToComeUp > INFO: Waiting until we see more replicas up: total=2 found=1 > timeoutin=178992 > Feb 12, 2013 1:19:09 PM org.apache.solr.cloud.ShardLeaderElectionContext > waitForReplicasToComeUp > INFO: Waiting until we see more replicas up: total=2 found=1 > timeoutin=178489 > Feb 12, 2013 1:19:09 PM org.apache.solr.cloud.ShardLeaderElectionContext > waitForReplicasToComeUp > INFO: Waiting until we see more replicas up: total=2 found=1 > timeoutin=177986 > > > And another one - let's assume I have 2 shards and one of them is down (both > - master and slave) for some reason. > What is happening now is that cluster returns 503 on the search request. Is > there a way to configure to get responses from other shard? > > > thanks. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/solrcloud-zookeeper-tp4039934.html > Sent from the Solr - User mailing list archive at Nabble.com.
