[
https://issues.apache.org/jira/browse/SOLR-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14721101#comment-14721101
]
Shawn Heisey commented on SOLR-7977:
------------------------------------
bq. do we really want users to have two different ways in which to set hostnames
I agree with your general philosophy of a simple configuration where the user
doesn't have to think too hard about what they are getting, but I do think we
need separate options available for the hostname in SolrCloud and the listen
interface(s).
I believe that the principle of least surprise for most people says "unless I
specifically say otherwise, I want Solr to listen on all interfaces" and that
this expectation will co-exist with "I want to specify the hostname in my
clusterstate." It's what I expect out of software. I admit that I am not most
people, but I do think that's a majority opinion. An example from our own
backyard: Apache httpd has separate config options for Listen, ServerName, and
ServerAlias. The IP address in the Listen parameter (which may be 0.0.0.0)
frequently has no direct connection to the ServerName or its aliases -- those
may exist on a firewall NAT rule or a load balancer.
Listening only on the IP address for the hostname provided, which is the only
reasonable thing to do if one option controls both settings, will disable
access on localhost. The URL for the admin UI that is given by the solr script
and our getting started documentation will not work.
> SOLR_HOST in solr.in.sh doesn't apply to Jetty's host property
> --------------------------------------------------------------
>
> Key: SOLR-7977
> URL: https://issues.apache.org/jira/browse/SOLR-7977
> Project: Solr
> Issue Type: Bug
> Components: security, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Labels: impact-medium
> Fix For: Trunk, 5.4
>
>
> [~sdavids] pointed out that the SOLR_HOST config option in solr.in.sh doesn't
> set Jetty's host property (solr.jetty.host) so it still binds to all net
> interfaces. Perhaps it should apply to jetty as well because the user
> explicitly wants us to bind to specific IP?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
