[
https://issues.apache.org/jira/browse/CASSANDRA-11181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115003#comment-16115003
]
Andy Tolbert commented on CASSANDRA-11181:
------------------------------------------
{quote}
I think we should simply be storing the broadcast_rpc_address in the
rpc_address column, since that's what we do for system.peers.
{quote}
+100, if {{rpc_address}} is set to 0.0.0.0, and {{broadcast_rpc_address}} is
set to something, you can't really use the {{rpc_address}} column in
{{system.local}}. I would consider that a bug.
> Add broadcast_rpc_address to system.local
> -----------------------------------------
>
> Key: CASSANDRA-11181
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11181
> Project: Cassandra
> Issue Type: Improvement
> Components: Distributed Metadata
> Reporter: Nick Bailey
> Labels: client-impacting
> Fix For: 4.x
>
>
> Right now it's impossible to get the broadcast_rpc_address of the node you
> are connected to via the drivers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
