You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Isidoro García Gutiérrez (Jira)" <ji...@apache.org> on 2021/04/02 18:49:01 UTC
[jira] [Assigned] (CASSANDRA-16386) Column rpc_address on
system_local ignores broadcast_rpc_address yaml setting
[ https://issues.apache.org/jira/browse/CASSANDRA-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Isidoro García Gutiérrez reassigned CASSANDRA-16386:
----------------------------------------------------
Assignee: Isidoro García Gutiérrez
> 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
> Assignee: Isidoro García Gutiérrez
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org