[
https://issues.apache.org/jira/browse/CASSANDRA-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917972#comment-13917972
]
Sylvain Lebresne commented on CASSANDRA-4501:
---------------------------------------------
How big of a deal is that to add a new native_transport_address to gossip? It's
not so much that I care about allowing to set thrift and the native transport
on different address, but it kind of bugs me that the native protocol reuse
rpc_address somewhat implicitly without having it's own setting, it's not
extremely consistent in the yaml and it makes it feels like the native
transport is somewhat of a 2nd class citizen compared to the thrift one. Not a
huge deal obviously, but figured that if we want to clean that up a bit for the
future, we should as well do it now before/simultaneously with CASSANDRA-5899
so it's coherent.
> Gossip the ip and port used by the native protocol
> --------------------------------------------------
>
> Key: CASSANDRA-4501
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4501
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 2.1
>
>
> Same as we gossip the rpc_address, we should add gossipping of the native
> transport address (including the port). CASSANDRA-4480 has one reason why we
> would want to do that.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
