[
https://issues.apache.org/jira/browse/CASSANDRA-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119623#comment-13119623
]
Hudson commented on CASSANDRA-3211:
-----------------------------------
Integrated in Cassandra-0.8 #357 (See
[https://builds.apache.org/job/Cassandra-0.8/357/])
check all interfaces for a match with split location before falling back to
random replica
patch by Brian ONeill; reviewed by jbellis for CASSANDRA-3211
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1178554
Files :
* /cassandra/branches/cassandra-0.8/CHANGES.txt
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/hadoop/ColumnFamilyRecordReader.java
> Enhanced IP resolution for machines with multiple network interfaces
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-3211
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3211
> Project: Cassandra
> Issue Type: Improvement
> Components: Hadoop
> Affects Versions: 0.6
> Environment: Mac OS X and Linux with machines that have multiple
> network interfaces whereby the IP associated with the split is not on the
> network interface associated with localhost.
> Reporter: Brian ONeill
> Priority: Minor
> Fix For: 0.8.7
>
> Attachments: trunk-3211.txt
>
>
> On unix machines that have multiple network interfaces whereby the IP
> associated with the split is not on the network interface associated with
> localhost, the getLocation method cannot find the proper IP and throws an
> exception "no connection available".
> I changed the implementation to use NetworkInterface instead of InetAddress
> using getLocalHost().
> This is more reliable. See the following references:
> http://stackoverflow.com/questions/5813194/inetaddress-getlocalhost-does-not-return-expected-ip-address-from-c-windows-sy
> http://stackoverflow.com/questions/4871451/inetaddress-getlocalhost-returns-wrong-result-when-hostname-is-64-chars
> http://www.jguru.com/faq/view.jsp?EID=790132
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
