[
https://issues.apache.org/jira/browse/SOLR-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe reopened SOLR-9386:
------------------------------
{quote}
I'm currently getting the following error when starting Solr in cloud mode
(bin/solr start -c) in master. Could be related to this ticket, but not sure.
2017-05-01 02:36:29.297 ERROR (main) [ ] o.a.s.c.SolrCore
null:java.lang.IllegalArgumentException: clientPort is not set
{quote}
Pretty sure this ^ is caused by the ZK upgrade. Reopening to address.
Prior to this issue, Solr did its own parsing of {{zoo.cfg}}, but after this
issue, Solr delegates to ZK's {{QuorumPeerConfig.parseProperties()}} to do so.
ZK's method (unlike Solr's previous parsing code) requires that {{clientPort}}
be specified in {{zoo.cfg}}.
Solr's check for missing {{clientPort}} configuration (and setting to
{{solrPort + 1000}} if absent) is currently performed *after* parsing
{{zoo.cfg}}. I have a patch I'm testing that moves supplying a default
{{clientPort}} to before {{QuorumPeerConfig.parseProperties()}}.
> Upgrade Zookeeper to 3.4.10
> ---------------------------
>
> Key: SOLR-9386
> URL: https://issues.apache.org/jira/browse/SOLR-9386
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Fix For: 6.6, master (7.0)
>
> Attachments: SOLR-9386.patch, SOLR-9386.patch, SOLR-9386.patch,
> zookeeper-3.4.8-upgrade-tests-pass.patch,
> zookeeper-3.4.9-upgrade-tests-fail.patch
>
>
> Zookeeper 3.4.10 release should be happening fairly soon, and the ZK issue
> blocking incorporation into Solr (ZOOKEEPER-2383) has a 3.4.10-targetted
> patch that fixes the test failures problem noted on SOLR-8724.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
