[
https://issues.apache.org/jira/browse/SOLR-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213728#comment-14213728
]
Erick Erickson commented on SOLR-6726:
--------------------------------------
Poking around a little more, mostly hacking around since I don't really know
what's going on,
it's bash scripting and I'm sitting in an airport....:
1> At first I wondered if it was a problem with just reading in the port, but
if I
hack bin/solr and change this line
declare -a CLOUD_PORTS=('8983' '7574' '8984' '7575');
to this line
declare -a CLOUD_PORTS=('8983' '7200' '7300' '7400');
the same thing occurs.
2> using this command: ./solr start -c -e cloud -z localhost:2181
3> If I change as above and put in the original ports, it's fine. (i.e., I get
prompted for node2 to go on 7200
and enter 7574 instead.
4> node2/logs/solr-7200-console.log consists of: "Error: Exception thrown by
the agent : java.lang.NullPointerException"
bonus question: Why is there a log for 8983 in node2 (which is where the 7200
core is supposed to be) and why does it contain the line:
org.apache.solr.core.CoresLocator – Looking for core definitions underneath
/Users/Erick/apache/trunk_6703/solr/server/solr?
> Specifying different ports with the new bin/solr script fails to bring up
> collection
> ------------------------------------------------------------------------------------
>
> Key: SOLR-6726
> URL: https://issues.apache.org/jira/browse/SOLR-6726
> Project: Solr
> Issue Type: Bug
> Reporter: Erick Erickson
> Assignee: Erick Erickson
>
> As I recall, I tried to specify different ports when bringing up 4 instances
> (7200, 7300, 7400) and the startup script failed. I'll confirm this and maybe
> propose a fix if I can reproduce. Assigning it to me so I make sure it's
> checked.
> I'm at Lucene Revolution this week, so if anyone wants to pick this up feel
> free.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
