You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Houston Putman (Jira)" <ji...@apache.org> on 2021/01/09 00:06:00 UTC

[jira] [Resolved] (SOLR-14999) Add built-in option to advertise Solr with a different port than Jetty listens on.

     [ https://issues.apache.org/jira/browse/SOLR-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Houston Putman resolved SOLR-14999.
-----------------------------------
    Fix Version/s: 8.8
       Resolution: Fixed

> Add built-in option to advertise Solr with a different port than Jetty listens on.
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-14999
>                 URL: https://issues.apache.org/jira/browse/SOLR-14999
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Houston Putman
>            Assignee: Houston Putman
>            Priority: Major
>             Fix For: 8.8
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently the default settings in {{solr.xml}} allow the specification of one port, {{jetty.port}} which the bin/solr script provides from the {{SOLR_PORT}} environment variable. This port is used twice. Jetty uses it to listen for requests, and the clusterState uses the port to advertise the address of the Solr Node.
> In cloud environments, it's sometimes crucial to be able to listen on one port and advertise yourself as listening on another. This is because there is a proxy that listens on the advertised port, and forwards the request to the server which is listening to the jetty port.
> Solr already supports having a separate Jetty port and Live Nodes port (examples provided in the dev-list discussion linked below). I suggest that we add this to the default solr config so that users can use the default solr.xml in cloud configurations, and the solr/bin script will enable easy use of this feature.
> There has been [discussion on this exact problem|https://mail-archives.apache.org/mod_mbox/lucene-dev/201910.mbox/%3CCABEwPvGFEggt9Htn%3DA5%3DtoawuimSJ%2BZcz0FvsaYod7v%2B4wHKog%40mail.gmail.com%3E] on the dev list already.
> I propose the new system property to be used for {{hostPort}} in the solr.xml. I am open to changing the name, but to me it is more descriptive than {{hostPort}}.
> {{-Dsolr.port.advertise}} and {{SOLR_PORT_ADVERTISE}} (env var checked in bin/solr).
> The xml field {{<hostPort>}} would not be changed however, just the system property that is used to fill the value in the default {{solr.xml}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org