Perhaps there is something preventing clean shutdown. Shutdown makes a best
effort attempt to publish DOWN for all the local cores.
Otherwise, yes, it's a little bit annoying, but full state is a combination
of the state entry and whether the live node for that replica exists or not.
- Mark
On W
Thank you Tomás for pointing to the JavaDoc
http://www.solr-start.com/javadoc/solr-lucene/org/apache/solr/common/cloud/Replica.State.html#ACTIVE
The Javadoc is quite clear. So this stale state.json is not an issue after
all.
However, it's very confusing that when a node goes down, state.json may
bq: You were probably referring to state.json
yep, I'm never sure whether people are on the old or new ZK versions.
OK, With Tomás' comment, I think it's explained... although confusing.
WDYT?
On Tue, Sep 8, 2015 at 10:03 AM, Arcadius Ahouansou
wrote:
> Hello Erick.
>
> Yes,
>
> 1> liveNodes
Hello Erick.
Yes,
1> liveNodes has N nodes listed (correctly): Correct, liveNodes is always
right.
2> clusterstate.json has N+M nodes listed as "active": clusterstate.json is
always empty as it's no longer being "used" in 5.3. You were
probably referring to state.json which is in individual coll
I believe this is expected in the current code. From Replica.State javadoc:
/**
* The replica's state. In general, if the node the replica is hosted on
is
* not under {@code /live_nodes} in ZK, the replica's state should be
* discarded.
*/
public enum State {
/**
* The r
Arcadius:
Hmmm. It may take a while for the cluster state to change, but I'm
assuming that this state persists for minutes/hours/days.
So to recap: If dump the entire ZK node from the root, you have
1> liveNodes has N nodes listed (correctly)
2> clusterstate.json has N+M nodes listed as "active"
On Sep 8, 2015 6:25 AM, "Erick Erickson" wrote:
>
> Perhaps the browser cache? What happens if you, say, use
> Zookeeper client tools to bring down the the cluster state in
> question? Or perhaps just refresh the admin UI when showing
> the cluster status
>
Hello Erick.
Thank you very much f
On Sep 8, 2015 6:25 AM, "Erick Erickson" wrote:
>
> Perhaps the browser cache? What happens if you, say, use
> Zookeeper client tools to bring down the the cluster state in
> question? Or perhaps just refresh the admin UI when showing
> the cluster status
>
Hello Erick.
Thank you very much f
Perhaps the browser cache? What happens if you, say, use
Zookeeper client tools to bring down the the cluster state in
question? Or perhaps just refresh the admin UI when showing
the cluster status
Shot in the dark,
Erick
On Mon, Sep 7, 2015 at 6:09 PM, Arcadius Ahouansou wrote:
> We are run
We are running the latest Solr 5.3.0
Thanks.
Hello.
In one of our test environment, we have a SolrCloud cluster of 8 SolrCloud
nodes and a quorum of 5 ZooKeeper node.
We have only 2 collections and all SolrCloud nodes are identical and have
a single replica of each collection.
I noticed that when I shut down one of the solr nodes and refr
11 matches
Mail list logo
