[
https://issues.apache.org/jira/browse/CASSANDRA-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408601#comment-15408601
]
Paulo Motta commented on CASSANDRA-11356:
-----------------------------------------
Updated {{NEWS.txt}} and added the following note to
{{doc/source/operating/snitch.rst}} on 3.9 and trunk:
bq. By default, Ec2MultiRegionSnitch advertises the public instance IP as
``rpc_address``, allowing cross-DC discovery by token-aware clients but this
may incur additional charges on EC2 for public IP access within the local DC if
a token-aware client is used. In order to override this behavior and restrict
token-aware clients to the local DC, set ``broadcast_rpc_address`` to the
instance's private IP.
After writing this, I wondered if we should provide this as an option on
{{Ec2MultiRegionSnitch}}, but then I thought that we should ultimately fix this
limitation by adding a {{broadcast_rpc_address}} column to the {{system.peers}}
table, and drivers would pick either the private {{rpc_address}} or the public
{{broadcast_rpc_address}} depending on where the client is located, but we
should probably fix this in another ticket. WDYT?
> 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)
