Colvin Cowie created SOLR-14503:
-----------------------------------
Summary: Solr does not respect waitForZk (SOLR_WAIT_FOR_ZK)
property
Key: SOLR-14503
URL: https://issues.apache.org/jira/browse/SOLR-14503
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 8.5.1, 8.4.1, 8.5, 8.3.1, 8.4, 8.3, 8.1.1, 7.7.3, 8.2, 8.1
Reporter: Colvin Cowie
When starting Solr in cloud mode, if zookeeper is not available within 30
seconds, then core container intialization fails and the node will not recover
when zookeeper is available.
I believe SOLR-5129 should have addressed this issue, however it doesn't quite
do so for two reasons:
#
[https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/servlet/SolrDispatchFilter.java#L297]
it calls {{SolrZkClient(String zkServerAddress, int zkClientTimeout)}} rather
than {{SolrZkClient(String zkServerAddress, int zkClientTimeout, int
zkClientConnectTimeout)}} so the DEFAULT_CLIENT_CONNECT_TIMEOUT of 30 seconds
is used
# bin/solr contains script to set -DwaitForZk from the SOLR_WAIT_FOR_ZK
environment property
[https://github.com/apache/lucene-solr/blob/master/solr/bin/solr#L2148] but
there is no corresponding assignment in bin/solr.cmd, while SOLR_WAIT_FOR_ZK
appears in the solr.in.cmd as an example.
I will attach a patch that fixes the above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
