You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Arcadius Ahouansou (JIRA)" <ji...@apache.org> on 2015/07/17 18:19:04 UTC
[jira] [Created] (SOLR-7806) SolrCloud to use 127.0.01 instead of
localhost
Arcadius Ahouansou created SOLR-7806:
----------------------------------------
Summary: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org