You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2013/08/09 17:15:49 UTC
[jira] [Created] (SOLR-5129) If zookeeper is down, SolrCloud nodes
will not start correctly, even if zookeeper is started later
Shawn Heisey created SOLR-5129:
----------------------------------
Summary: 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: Bug
Components: SolrCloud
Affects Versions: 4.4
Reporter: Shawn Heisey
Fix For: 4.5, 5.0
Summary of report from user on mailing list:
If zookeeper is down 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org