Description
Originally we didn't rely on jetty.port as it's container specific - but rather than require you specify the port twice in this case, we should simply use jetty.port when it's there.
The example from the SolrCloud wiki:
java -Djetty.port=7574 -DhostPort=7574 -DzkHost=localhost:9983 -jar start.jar
instead becomes:
java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
We should also look at simply specifying the shard name in this example case (see the solrwiki examples) by system property rather than asking the user to edit solr.xml.
Attachments
Issue Links
- is related to
-
SOLR-14999 Add built-in option to advertise Solr with a different port than Jetty listens on.
- Resolved