[
https://issues.apache.org/jira/browse/CASSANDRA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850629#action_12850629
]
Benjamin Black commented on CASSANDRA-666:
------------------------------------------
Looking at Derek's code, the EC2Snitch is trying to use comparisons between EC2
IP addresses to guess proximity. The reliable technique is examining the
instance metadata to see in which availability zones the nodes are. See my
ec2snitch recipe for an example of how to use that information as a proxy for
rack and datacenter. I do not understand the need for a new placement strategy,
either.
> Making Cassandra EC2 Aware
> --------------------------
>
> Key: CASSANDRA-666
> URL: https://issues.apache.org/jira/browse/CASSANDRA-666
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.6
> Environment: replication strategy, endpoints
> Reporter: Derek Smith
> Assignee: Derek Smith
> Priority: Trivial
> Attachments: contrib-ec2-aware-1.1.tar.gz
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> There are no current replication strategies to deal with different data
> centers in an EC2 cluster. The IP address comparisons used in the current
> implementations aren't enough to guarantee that an endpoint is in the same
> datacenter. By supplying the access and secret key to a client's AWS
> account, Cassandra should use the amazon-ec2 java library to access
> information about each endpoint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
