[ https://issues.apache.org/jira/browse/SOLR-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316499#comment-14316499 ]
Hoss Man commented on SOLR-7099: -------------------------------- i've mentioned this in the past: ideally the _example_ mode of bin/solr will launch a single node zk server for you as needed, but will do so using a script and echo out what script command it ran. (similar to how it echos out collection creation / health check commands) when you run solr in (non-example) cloud mode, it should expect zk to already be running and by this point you should either already know what you need to setup a zk quorom, or you will remember that bin/solr has a command line option to launch solr that you saw when you were running the examples > 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: SolrCloud > Reporter: Timothy Potter > > 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 (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org