Details
-
New Feature
-
Status: Resolved
-
Normal
-
Resolution: Won't Fix
-
None
-
None
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.
Attachments
Attachments
Issue Links
- is blocked by
-
CASSANDRA-4501 Gossip the ip and port used by the native protocol
- Resolved