cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11596) Add native transport port to system.peers
Date Mon, 06 Feb 2017 20:49:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854718#comment-15854718
] 

Ariel Weisberg commented on CASSANDRA-11596:
--------------------------------------------

As part of this ticket I don't believe it has to change since system.peers is read using the
existing wire protocol.

> 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.15#6346)

Mime
View raw message