[
https://issues.apache.org/jira/browse/SOLR-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128284#comment-16128284
]
Hrishikesh Gadre commented on SOLR-5129:
----------------------------------------
[~caomanhdat] Couple of nits in your patch,
Instead of
{code}
int startUpZkTimeOut = Integer.parseInt(System.getProperty("startUpZkTimeOut",
"60"));
{code}
How about
{code}
int startUpZkTimeOut = Integer. getInteger("startUpZkTimeOut", 60);
{code}
Also ideally this parameter should be exposed via solr.xml (e.g. under
solrcloud section). What do you think?
> 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: [email protected]
For additional commands, e-mail: [email protected]
