[
https://issues.apache.org/jira/browse/SOLR-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715395#comment-14715395
]
Shawn Heisey edited comment on SOLR-7977 at 8/26/15 7:49 PM:
-------------------------------------------------------------
bq. I can envision situations where the host that the user wants to include in
zookeeper is entirely different
In any sanely set up network, those two will of course always be identical ...
but users have a way of inventing strange networking setups with address
translation where not everything matches up the way it would in a
straightforward network. Also, a user may want to specify the hostname to
SolrCloud, but still listen on all interfaces, not just the one specified by
the hostname.
was (Author: elyograg):
bq. I can envision situations where the host that the user wants to include in
zookeeper is entirely different
In any sanely set up network, those two will of course always be identical ...
but users have a way of inventing strange networking setups with address
translation where not everything matches up the way it would in a
straightforward network.
> 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: [email protected]
For additional commands, e-mail: [email protected]
