[
https://issues.apache.org/jira/browse/CASSANDRA-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197379#comment-15197379
]
Paulo Motta commented on CASSANDRA-11356:
-----------------------------------------
I'm not sure we should even be setting {{broadcast_rpc_address}} on EC2MRS.
While setting {{broadcast_address}} is useful to the snitch's objective of
making nodes from different dcs connect over the public address for internal
communication, {{broadcast_rpc_address}} is a deployment option independent of
EC2MRS choice. I'd be in favor of not setting this at all on EC2MRS and adding
an upgrade notice for users who've been relying on this behavior.
> EC2MRS ignores broadcast_rpc_address setting in cassandra.yaml
> --------------------------------------------------------------
>
> Key: CASSANDRA-11356
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11356
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Thanh
> Fix For: 2.2.x, 3.x
>
>
> EC2MRS ignores broadcast_rpc_address setting in cassandra.yaml. This is
> problematic for those users who were using EC2MRS with an internal
> rpc_address before the change introduced in
> [CASSANDRA-5899|https://issues.apache.org/jira/browse/CASSANDRA-5899],
> because the change results in EC2MRS always using the public ip regardless of
> what the user has set for broadcast_rpc_address.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
