[
https://issues.apache.org/jira/browse/SOLR-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720973#comment-14720973
]
Shalin Shekhar Mangar commented on SOLR-7977:
---------------------------------------------
Thanks Shawn. Yeah, earlier we had no control of the application server and
how/where it listens. But now that we have got rid of the war and want to view
Solr as one black box application, do we really want users to have two
different ways in which to set hostnames? One to bind to and another way to
send requests to (for inter-shard requests)?
I propose that we get rid of such funny business and have one way of
configuring host names which are applicable throughout. If SOLR_HOST is not
specified, we can continue to listen on all addresses (the default right now)
and select one for inter-shard requests as we do today.
> 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
