You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2016/12/15 20:57:58 UTC

[jira] [Assigned] (CASSANDRA-11596) Add native transport port to system.peers

     [ https://issues.apache.org/jira/browse/CASSANDRA-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ariel Weisberg reassigned CASSANDRA-11596:
------------------------------------------

    Assignee: Ariel Weisberg

> 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
>            Assignee: Ariel Weisberg
>            Priority: Minor
>              Labels: lhf
>
> 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)