cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Michallat (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11596) Add native transport port to system.peers
Date Tue, 03 Oct 2017 21:02:00 GMT

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

Olivier Michallat commented on CASSANDRA-11596:
-----------------------------------------------

I'm afraid it does, you'll need the port in {{STATUS_CHANGE}} events.

> 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.4.14#64029)

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


Mime
View raw message