Houston Putman created SOLR-15442:
-------------------------------------
Summary: Syncronize the port and host variables for Solr
Key: SOLR-15442
URL: https://issues.apache.org/jira/browse/SOLR-15442
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Houston Putman
Assignee: Houston Putman
There are 4 options for specifying host and port in Solr.
These can be organized as such:
* {{host}} - This is the host that is advertised by the Solr node in the ZK
live nodes
* {{solr.jetty.host}} - This is the host that jetty binds to, and only accepts
requests to.
* {{jetty.port}} - This is the port that jetty binds to, and accepts requests
to.
* {{solr.port.advertise}} - This is the port that is advertised by the Solr
node in the ZK live nodes.
In order to synchronize these, we can rename them to:
* {{solr.host.advertise}} <- {{host}}
* {{solr.host.bind}} <- {{solr.jetty.host}} (could also be {{solr.host.listen}})
* {{solr.port.advertise}}
* {{solr.port.listen}} <- {{jetty.port}} and {{solr.jetty.https.port}}
These would come with compatible env-vars in bin/solr, that are backwards
compatible with the env vars currently accepted.
Unfortunately there is no way to have backwards compatibility with the jetty
config variables, since you can default the value of one variable with the
value of another. However we can keep backwards compatibility with the
advertised variables, as those are used by Solr alone.
The new names are up for debate, but it's certainly something that we should
make straightforward. This is a good thing to shoot for 9.0, being a major
release where we can have these backwards-incompatible name changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
