[
https://issues.apache.org/jira/browse/SOLR-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187127#comment-14187127
]
Shalin Shekhar Mangar commented on SOLR-6610:
---------------------------------------------
The way the ZkController.publishAndWaitForDownStates is written, it checks if
the live_nodes exist and then it tries to publish and wait but that's not
really correct. It should check if live_nodes exists and it has at least one
childred. Then only we can be sure that there will be an overseer to process
the state requests.
I've seen this problem on cluster restarts where ZK already has /live_nodes
existing but without any children (which are ephemeral of course). But I've
never seen this problem on individual node restarts when an overseer exists in
the cluster already.
> In stateFormat=2, ZkController.publishAndWaitForDownStates always times out
> ---------------------------------------------------------------------------
>
> Key: SOLR-6610
> URL: https://issues.apache.org/jira/browse/SOLR-6610
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Jessica Cheng Mallet
> Assignee: Noble Paul
> Labels: solrcloud
>
> Using stateFormat=2, our solr always takes a while to start up and spits out
> this warning line:
> {quote}
> WARN - 2014-10-08 17:30:24.290; org.apache.solr.cloud.ZkController; Timed
> out waiting to see all nodes published as DOWN in our cluster state.
> {quote}
> Looking at the code, this is probably because
> ZkController.publishAndWaitForDownStates is called in ZkController.init,
> which gets called via ZkContainer.initZookeeper in CoreContainer.load before
> any of the stateFormat=2 collection watches are set in the
> CoreContainer.preRegisterInZk call a few lines later.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
