[CASSANDRA-7544] Allow storage port to be configurable per node

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Assignee: Ariel Weisberg
• Reporter: Sam Overton

Authors

Ariel Weisberg

Reviewers

Jason Brown

• Created: 15/Jul/14 00:40
• Updated: 15/May/20 08:06
• Resolved: 08/Feb/18 21:00

Description

Currently storage_port must be configured identically on all nodes in a cluster and it is assumed that this is the case when connecting to a remote node.

This prevents running in any environment that requires multiple nodes to be able to bind to the same network interface, such as with many automatic provisioning/deployment frameworks.

The current solutions seems to be

• use a separate network interface for each node deployed to the same box. This puts a big requirement on IP allocation at large scale.
• allow multiple clusters to be provisioned from the same resource pool, but restrict allocation to a maximum of one node per host from each cluster, assuming each cluster is running on a different storage port.

It would make operations much simpler in these kind of environments if the environment provisioning the resources could assign the ports to be used when bringing up a new node on shared hardware.

The changes required would be at least the following:
1. configure seeds as IP:port instead of just IP
2. gossip the storage port as part of a node's ApplicationState
3. refer internally to nodes by hostID instead of IP, since there will be multiple nodes with the same IP

(1) & (2) are mostly trivial and I already have a patch for these. The bulk of the work to enable this is (3), and I would structure this as a separate pre-requisite patch.

Issue Links

• causes: CASSANDRA-14211 Revert ProtocolVersion changes from CASSANDRA-7544
• is related to: CASSANDRA-11596 Add native transport port to system.peers
• is related to: CASSANDRA-15334 Restore java-driver back to upstream code, using new implementation for dynamic port discovery