You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2018/04/27 04:57:00 UTC
[jira] [Commented] (SOLR-5129) Timeout property for waiting ZK get
started
[ https://issues.apache.org/jira/browse/SOLR-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16455761#comment-16455761 ]
David Smiley commented on SOLR-5129:
------------------------------------
ZkFailoverTest.setupCluster adds a config "conf1" but it is not actually used in the test; instead the "_default" config is used.
> Timeout property for waiting ZK get started
> -------------------------------------------
>
> 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
> Assignee: Cao Manh Dat
> Priority: Minor
> Fix For: 7.1
>
> Attachments: SOLR-5129.patch, 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org