[
https://issues.apache.org/jira/browse/SOLR-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631629#comment-14631629
]
Mark Miller commented on SOLR-7806:
-----------------------------------
bq. I have looked around IMHO, the usage of 'localhost' in the solr code base
may be leading to this kind of issues
Where do you see the usage? At one time we had tried to switch all the
localhost usage to 127.0.0.1 - either we missed some or some has slipped back
in.
> 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
>
> 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]
