[
https://issues.apache.org/jira/browse/SOLR-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645175#comment-14645175
]
Arcadius Ahouansou commented on SOLR-7806:
------------------------------------------
Hello [~thetaphi]
IMHO, localhost is being used as a fall back if we cannot get an external
(public or private) IP for the current node.
If a proper IPv6 IP is found, Solr should still work for IPv6 hosts...
Note that 127.0.0.1 is already being put into good usage in few places such as
https://github.com/apache/lucene-solr/blob/19587a20257f5f23a95c31b74b08d36a512042f3/solr/core/src/java/org/apache/solr/cloud/ZkController.java#L567
And using 127.0.0.1 helps avoid resolving localhost into some undesirable IP as
it is the case on VPN.
Consistency in the code base may also be something we should consider.
> SolrCloud to use 127.0.01 instead of localhost
> ----------------------------------------------
>
> Key: SOLR-7806
> URL: https://issues.apache.org/jira/browse/SOLR-7806
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.2.1
> Environment: Linux
> Mac OS X
> Reporter: Arcadius Ahouansou
> Attachments: SOLR-7806.patch
>
>
> A colleague is having an issue very similar to the one described at
> http://muddyazian.blogspot.co.uk/2015/03/how-to-get-solr-500-quick-start.html
> He is running on the latest Arch Linux, and he gets that issue only when he
> connects to the office network.
> We also have another case when this happens only when a colleague is
> connected to the office network via VPN from his mac.
> I have looked around IMHO, the usage of 'localhost' in the solr code base may
> be leading to this kind of issues where the resolved IP is not route-able.
> Does it make any sense to replace all usage of 'localhost' in the code base
> by 127.0.01?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
