[
https://issues.apache.org/jira/browse/SOLR-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045385#comment-15045385
]
Xavier commented on SOLR-7977:
------------------------------
[~elyograg], I'd agree that two different option variables are a good idea. For
instance, in my (small) deployment, I have a single solr server, thus I don't
really care how SolrCloud addresses the server; but I care which IP is used to
listen for requests. Right now, following [~shalinmangar]'s recommendation, I'm
directly passing the {{jetty.host}} parameter using {{$SOLR_OPTS}}. However,
that's a temporary workaround, especially since the fact that the solr black
box uses jetty is an implementation detail.
Adding a {{$SOLR_LISTEN}} or {{$SOLR_BIND_IP}} variable to the _solr.in.sh_
file, which then gets translated to the appropriate parameter, would, in my
opinion, be the best way of solving the problem, and if the internal
implementation changes (solr moves off an embedded jetty), the configuration
files will need little to no editing.
> 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: 5.4, Trunk
>
>
> [~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]
