[jira] [Updated] (SOLR-5129) If zookeeper is down, SolrCloud nodes will not start correctly, even if zookeeper is started later

["Cao Manh Dat (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cao Manh Dat updated SOLR-5129:
-------------------------------
    Attachment: SOLR-5129.patch

I think this issue can be solved by adding a system property for larger timeout. I called it {{startUpZkTimeOut}} in the patch, better name for the property is welcome :)

> 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