Details
-
Bug
-
Status: Open
-
Normal
-
Resolution: Unresolved
-
None
-
None
-
Correctness
-
Low
-
Low Hanging Fruit
-
User Report
-
All
-
None
Description
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.