[jira] [Commented] (SOLR-7806) SolrCloud to use 127.0.01 instead of localhost
[ https://issues.apache.org/jira/browse/SOLR-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7806) SolrCloud to use 127.0.01 instead of localhost
[ https://issues.apache.org/jira/browse/SOLR-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635221#comment-14635221 ] Uwe Schindler commented on SOLR-7806: - -1 to this patch, because it makes use of Solr impossible on IPv6-only configurations. localhost is neutral (one could also argue to use ::1 instead of 127.0.0.1). 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7806) SolrCloud to use 127.0.01 instead of localhost
[ https://issues.apache.org/jira/browse/SOLR-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635201#comment-14635201 ] Arcadius Ahouansou commented on SOLR-7806: -- Please see attached patch [~markrmil...@gmail.com] 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7806) SolrCloud to use 127.0.01 instead of localhost
[ https://issues.apache.org/jira/browse/SOLR-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635198#comment-14635198 ] Arcadius Ahouansou commented on SOLR-7806: -- I have taken note [~anders5737] 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7806) SolrCloud to use 127.0.01 instead of localhost
[ https://issues.apache.org/jira/browse/SOLR-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631584#comment-14631584 ] Erick Erickson commented on SOLR-7806: -- Please raise these kinds of things on the user's list before raising a JIRA. 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7806) SolrCloud to use 127.0.01 instead of localhost
[ https://issues.apache.org/jira/browse/SOLR-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
