cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-94) Remove mix of ip-address and hostnames
Date Wed, 22 Apr 2009 21:00:49 GMT


Jonathan Ellis updated CASSANDRA-94:

    Fix Version/s: 0.3

> Remove mix of ip-address and hostnames 
> ---------------------------------------
>                 Key: CASSANDRA-94
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: trunk
>            Reporter: Per Mellqvist
>            Priority: Minor
>             Fix For: 0.3
>   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.

View raw message