[ https://issues.apache.org/jira/browse/SOLR-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cao Manh Dat resolved SOLR-5129. -------------------------------- Resolution: Fixed Fix Version/s: (was: 6.0) (was: 4.9) 7.1 thanks all! > 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 (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org