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" Doesn't sound right to me, but I'll have to let people who are deep into that code speculate from here. Best, Erick On Tue, Sep 8, 2015 at 1:13 AM, Arcadius Ahouansou <arcad...@menelic.com> wrote: > On Sep 8, 2015 6:25 AM, "Erick Erickson" <erickerick...@gmail.com> 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 for answering. > I did use the ZooInspetor tool to check the state.json in all 5 zk nodes > and they are all out of date and identical to what I get through the tree > view in sole admin ui. > > Looking at the source code cloud.js that correctly display nodes as "gone" > in the graph view, it calls the end point /zookeeper?wt=json and relies on > the live nodes to mark a node as down instead of status.json. > > Thanks. > >> Shot in the dark, >> Erick >> >> On Mon, Sep 7, 2015 at 6:09 PM, Arcadius Ahouansou <arcad...@menelic.com> > wrote: >> > We are running the latest Solr 5.3.0 >> > >> > Thanks.
