[
https://issues.apache.org/jira/browse/CASSANDRA-11181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421285#comment-17421285
]
Stefan Miklosovic commented on CASSANDRA-11181:
-----------------------------------------------
[~azotcsit], do you have any preference here in regards of what Mick said
previously in his last comment in this ticket about listen_on_broadcast_address
param? I feel that that is the right thing to do - if you follow the link he
posted - but I am not sure what consequencies it has at other places where this
field might be used.
Additionally, I think we should also start to expose ssl_storage_port. I yet
have to check what the introduction of a new field means here in a broader
context and if we are safe to do that. We might also focus more at 16830 and if
we do that first, I think the necessity to expose ssl_storage_port will cease
to exist but I am afraid that until then it is still valid to expose it.
> 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: Legacy/Distributed Metadata
> Reporter: Nick Bailey
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
