You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Seth Fitzsimmons (JIRA)" <ji...@apache.org> on 2010/04/05 20:09:27 UTC
[jira] Commented: (CASSANDRA-666) Making Cassandra EC2 Aware
[ https://issues.apache.org/jira/browse/CASSANDRA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853472#action_12853472 ]
Seth Fitzsimmons commented on CASSANDRA-666:
--------------------------------------------
Instance metadata is available from http://169.254.169.254/latest/meta-data/placement/availability-zone/ when on an EC2 instance.
> 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.