"base_url":"http://172.29.24.75:8983/solr";,
"leader":"true"},
"core_node150":{
"state":"recovering",
"core":"kla_collection_shard25_re
ardLeaderElectionContextBase$1.execute(ElectionContext.java:142)
> at
> org.apache.solr.common.util.RetryUtil.retryOnThrowable(RetryUtil.java:34)
>
> Matt
>
>
> -Original Message-
> From: Matt Kuiper [mailto:matt.kui...@issinc.com]
> Sent: Wednesday, April 08, 2015
at
org.apache.solr.common.util.RetryUtil.retryOnThrowable(RetryUtil.java:34)
Matt
-Original Message-
From: Matt Kuiper [mailto:matt.kui...@issinc.com]
Sent: Wednesday, April 08, 2015 4:36 PM
To: solr-user@lucene.apache.org
Subject: RE: Clusterstate - state active
Erick, Anshum,
: 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 wh
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
Hi Matt,
If it's the replica state that you're looking at, yes, it means that the
Replica is in sync with the leader and serving/ready to serve requests.
On Wed, Apr 8, 2015 at 2:58 PM, Matt Kuiper wrote:
> Hello,
>
> When creating a new replica, and the state is recorded as active with in
> ZK
