cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address
Date Fri, 05 Apr 2013 18:23:19 GMT


Jonathan Ellis commented on CASSANDRA-5400:

The pain of having an initClient entry point to StorageService and a "use it if it's useful;
don't complain if it breaks" policy for StorageProxy is approximately zero, so I'm okay with
keeping it around.  Then again, the tendency for it to code rot does seem to indicate that
nobody's really actively using it, so I'd be fine with removing it too.  (Although part of
me does want to port YCSB to it...  I bet that's one reason Voldemort tends to beat us at
latency benchmarks.)
> Allow multiple ports to gossip from a single IP address
> -------------------------------------------------------
>                 Key: CASSANDRA-5400
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>    Affects Versions: 2.0
>            Reporter: Carl Yeksigian
>            Assignee: Carl Yeksigian
>             Fix For: 2.0
>         Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch
> If a fat client is running on the same machine as a Cassandra node, the fat client must
be allocated a new IP address. However, since the node is now a part of the gossip, the other
nodes in the ring must be able to talk to it. This means that a local only address (127.0.0.n)
won't actually work for the rest of the ring.
> This also would allow for multiple Cassandra service instances to run on a single machine,
or from a group of machines behind a NAT.
> The change is simple in concept: instead of using an InetAddress, use a different class.
Instead of using an InetSocketAddress, which would still tie us to using InetAddress, I've
added a new class, "CassandraInstanceEndpoint". The serializer allows for reading a serialized
Inet4Address or Inet6Address; also, the message service can still communicate with non-CassandraInstanceEndpoint
aware code.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message