You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2017/08/15 21:25:01 UTC
[jira] [Commented] (SOLR-5129) If zookeeper is down, SolrCloud
nodes will not start correctly, even if zookeeper is started later
[ https://issues.apache.org/jira/browse/SOLR-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127887#comment-16127887 ]
Varun Thacker commented on SOLR-5129:
-------------------------------------
How about {{waitForZK}} ? I'm not super convinced with the name either but throwing it out there
> If zookeeper is down, SolrCloud nodes will not start correctly, even if zookeeper is started later
> --------------------------------------------------------------------------------------------------
>
> Key: SOLR-5129
> URL: https://issues.apache.org/jira/browse/SOLR-5129
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.4
> Reporter: Shawn Heisey
> Priority: Minor
> Fix For: 4.9, 6.0
>
> Attachments: SOLR-5129.patch
>
>
> Summary of report from user on mailing list:
> If zookeeper is down or doesn't have quorum when you start Solr nodes, they will not function correctly, even if you later start zookeeper. While zookeeper is down, the log shows connection failures as expected. When zookeeper comes back, the log shows:
> INFO - 2013-08-09 15:48:41.528; org.apache.solr.common.cloud.ConnectionManager; Client->ZooKeeper status change trigger but we are already closed
> At that point, Solr (admin UI and all other functions) does not work, and won't work until it is restarted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org