[CASSANDRA-5400] Allow multiple ports to gossip from a single IP address

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Won't Fix
• Fix Version/s: 2.0 beta 1
• Assignee: Carl Yeksigian
• Reporter: Carl Yeksigian

Authors

Carl Yeksigian

Reviewers

Brandon Williams

• Created: 29/Mar/13 00:23
• Updated: 16/Apr/19 09:32
• Resolved: 05/Apr/13 18:32

Description

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.

Issue Links

• is blocked by: CASSANDRA-4501 Gossip the ip and port used by the native protocol