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 2018/01/25 20:32:01 UTC

[jira] [Resolved] (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 resolved CASSANDRA-11596.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.0-

Fixed by CASSANDRA-7544.

> 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
>             Fix For: 4.0-
>
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org