[
https://issues.apache.org/jira/browse/SOLR-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760905#comment-17760905
]
Eric Pugh commented on SOLR-7099:
---------------------------------
It's been 8 years since the last comment, and I'm thinking that instead of
separate process, at this point, for basic Solr setups, we should actually
embrace the embedded ZK and use it. I've run small single node Solr setups
for years with no issues using embedded ZK.
See this progression of scaling...
https://miro.com/app/board/o9J_lm8BmXE=/?moveToWidget=3458764558006503531&cot=14
> bin/solr -cloud mode should launch a local ZK in its own process using
> zkcli's runzk option (instead of embedded in the first Solr process)
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7099
> URL: https://issues.apache.org/jira/browse/SOLR-7099
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools, SolrCloud
> Reporter: Timothy Potter
> Priority: Major
>
> Embedded ZK is great for unit testing and quick examples, but as soon as
> someone wants to restart their cluster, embedded mode causes a lot of issues,
> esp. if you restart the node that embeds ZK. Of course we don't want users to
> have to install ZooKeeper just to get started with Solr either.
> Thankfully, ZkCLI already includes a way to launch ZooKeeper in its own
> process but still within the Solr directory structure. We can hide the
> details and complexity of working with ZK in the bin/solr script. The
> solution to this should still make it very clear that this is for getting
> started / examples and not to be used in production.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
