[jira] Assigned: (CASSANDRA-94) Remove mix of ip-address and hostnames

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-94:
---------------------------------------

    Assignee: Jonathan Ellis

> Remove mix of ip-address and hostnames 
> ---------------------------------------
>
>                 Key: CASSANDRA-94
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-94
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Per Mellqvist
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.3
>
>         Attachments: 0001-switch-to-IP-everywhere.patch, 0002-rename-getHostName-getHostAddress-since-it-should.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The mix of ip-address and hostnames may cause confusion and problems.
> One example is that the EndPoint is internally represented as a four byte IPv4 address in the gossip messages, but upon arrival there is a reverse-lookup into a hostname that is used to create the new EndPoint java object on the receiver side. This is likely to cause problems if a fully qualified hostname is used on one end but the reverse lookup returns just a short machine name, or vice versa.
> It also has the strange effect that if you configure ListenAddress using IP-addresses it works only if it is NOT possible to do a reverse lookup of those addresses.
> Suggest FBUtilities.getHostName() is renamed to getHostAddress() and made to always return the string representation of the IPv4 address.
> Additionally EndPoint.fromBytes() should not attempt a reverse lookup, but just convert the four byte wire format of the IP to the string representation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.