You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2014/03/16 05:54:45 UTC
[jira] [Updated] (SOLR-4441) Developer Curb Appeal: one laptop,
multiple Solr nodes, consider auto-negotiating Solr and ZooKeeper ports
[ https://issues.apache.org/jira/browse/SOLR-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-4441:
-------------------------------
Fix Version/s: (was: 4.7)
4.8
> Developer Curb Appeal: one laptop, multiple Solr nodes, consider auto-negotiating Solr and ZooKeeper ports
> ----------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4441
> URL: https://issues.apache.org/jira/browse/SOLR-4441
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.1
> Reporter: Mark Bennett
> Fix For: 4.8
>
>
> A common usage scenario for a developer is to fire up multiple SolrCloud nodes on his/her laptop.
> When doing this, the second instance of Solr has to include the -Djetty.port=1234 parameter.
> Also, I believe since the embedded ZooKeeper's port defaults to SolrPort+1000, you also have to specify the -zkHost parameter, even though you're going to be using localhost.
> If would be nice if Solr noticed that it was already running and would automatically pick a different port, maybe 10 down from the most recently used port.
> It would also convenient if the embedded ZooKeeper could also figure this out, and look for zkmaster on some ports on localhost.
> I realize this is now how things would be deployed in production. This is just to get developers up quickly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org