[
https://issues.apache.org/jira/browse/CASSANDRA-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416350#comment-15416350
]
Jason Brown commented on CASSANDRA-11356:
-----------------------------------------
I'm +1 on the patch except for two minor issues:
- is 2.2 in critical-fixes only mode now? If so, let's only commit to 3.0 and
higher
- Can we add a couple of (simple) tests for
{{FBUtliities#getBroadcastRpcAddress}}? I can easily see that the functionality
is correct *now*, I'm just worried about the future if/when we move things
around and we accidentally break things.
> 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
> Assignee: Paulo Motta
> 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)
