Details
-
Improvement
-
Status: Resolved
-
Low
-
Resolution: Fixed
Description
Is there any reason why the native transport port is not being stored in system.peers along the rpc broadcast address and transmitted to the connected drivers?
I would love to have that feature, that would allow me to "hide" my cluster behind a reverse NAT or LB and only consume one external IP address and forward packets based on the port the client is connecting to.
I guess it makes sense to provide the complete socket information instead of just the address and using a default port setting on the client to complete the connection information.
Attachments
Issue Links
- relates to
-
CASSANDRA-7544 Allow storage port to be configurable per node
- Resolved
-
CASSANDRA-15530 Update CHANGES.txt with Add cross-DC latency metrics (CASSANDRA-11569)
- Resolved