[
https://issues.apache.org/jira/browse/CASSANDRA-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16386:
-----------------------------------------
Bug Category: Parent values: Correctness(12982)
Complexity: Low Hanging Fruit
Component/s: Local/Other
Discovered By: User Report
Severity: Low
Status: Open (was: Triage Needed)
Looks like this is since inception in CASSANDRA-9436. A case for changing this
to broadcast_rpc_address if set can easily be made, since if set, rpc_address
is presumably useless (0.0.0.0)
> Column rpc_address on system_local ignores broadcast_rpc_address yaml setting
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-16386
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16386
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
> Reporter: João Reis
> Priority: Normal
>
> While troubleshooting a driver issue I ran into a potential C* issue
> regarding the {{rpc_address}} and {{broadcast_rpc_address}} yaml settings. On
> {{system.peers}} I see that the {{rpc_address}} column is populated with the
> {{broadcast_rpc_address}} setting when {{rpc_address}} is {{0.0.0.0}} but
> this is not the same behavior for the {{system.local}} table.
> On {{system.local}}, {{rpc_address}} is returned as {{0.0.0.0}} even if
> {{broadcast_rpc_address}} is set. In my opinion the {{rpc_address}} on
> {{system.local}} should also be populated with the {{broadcast_rpc_address}}
> setting if {{rpc_address}} is {{0.0.0.0}}.
> I tested this with C* 3.11.8, 4.0-beta2 and 4.0-beta4 so it looks like this
> behavior has been like this for a while now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
