lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Bennett (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-4441) Developer Curb Appeal: one laptop, multiple Solr nodes, consider auto-negotiating Solr and ZooKeeper ports
Date Mon, 11 Feb 2013 22:09:12 GMT
Mark Bennett created SOLR-4441:
----------------------------------

             Summary: 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.2


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 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message