[
https://issues.apache.org/jira/browse/SOLR-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743334#comment-13743334
]
Alan Woodward commented on SOLR-5172:
-------------------------------------
bq. You need to simply use matching ports
Sure, but you need to specify the actual zk port in the zkhost line, and then
port - 1000 as the solrport parameter (which isn't used for anything else). I
found it a bit confusing.
Re. embedded ensembles, if the consensus is that we still want to support them,
then I'll add them back in - I'd got the impression that we were really trying
to discourage using embedded ZK servers in production, but if the plan is to
improve embedded mode over time then clearly we need to support ensembles now.
bq. Some open jiras for ZK should help with this
Do you have any pointers to specific JIRA tickets? I'm still getting my head
round the ZK internals, would be interested to see what sort of improvements we
could make. The completely different API for standalone ZK and ensembles is
doing my head in a bit, for a start...
> Start embedded zk servers before CoreContainer loads
> ----------------------------------------------------
>
> Key: SOLR-5172
> URL: https://issues.apache.org/jira/browse/SOLR-5172
> Project: Solr
> Issue Type: Improvement
> Reporter: Alan Woodward
> Priority: Minor
> Attachments: SOLR-5172.patch
>
>
> In SOLR-4718 we allowed solr.xml to be read from Zookeeper in cloud setups.
> However, this doesn't work with an embedded ZK server because it doesn't
> start until CoreContainer.load() is called, by which time solr.xml has
> already been loaded. We should move the embedded ZK startup/shutdown logic
> out of CoreContainer and into SolrDispatchFilter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
