cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nico Haller (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-11596) Add native transport port to system.peers
Date Mon, 18 Apr 2016 15:43:25 GMT
Nico Haller created CASSANDRA-11596:
---------------------------------------

             Summary: Add native transport port to system.peers
                 Key: CASSANDRA-11596
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11596
             Project: Cassandra
          Issue Type: Improvement
          Components: Distributed Metadata
            Reporter: Nico Haller
            Priority: Minor


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message