You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Derek Smith (JIRA)" <ji...@apache.org> on 2010/01/04 19:57:55 UTC
[jira] Created: (CASSANDRA-666) Making Cassandra EC2 Aware
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.5
Environment: replication strategy, endpoints
Reporter: Derek Smith
Assignee: Derek Smith
Priority: Trivial
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.
[jira] Commented: (CASSANDRA-666) Making Cassandra EC2 Aware
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796350#action_12796350 ]
Jonathan Ellis commented on CASSANDRA-666:
------------------------------------------
Contributing an EC2-aware EndpointSnitch to contrib/ is fine.
> 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.5
> Environment: replication strategy, endpoints
> Reporter: Derek Smith
> Assignee: Derek Smith
> Priority: Trivial
> 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.
[jira] Commented: (CASSANDRA-666) Making Cassandra EC2 Aware
Posted by "Benjamin Black (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846223#action_12846223 ]
Benjamin Black commented on CASSANDRA-666:
------------------------------------------
The AWS credentials are not required. Instance metadata placement_availability_zone provides the needed information.
> 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.5
> Environment: replication strategy, endpoints
> Reporter: Derek Smith
> Assignee: Derek Smith
> Priority: Trivial
> 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.
[jira] Updated: (CASSANDRA-666) Making Cassandra EC2 Aware
Posted by "Derek Smith (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Derek Smith updated CASSANDRA-666:
----------------------------------
Affects Version/s: (was: 0.5)
0.6
> 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
> 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.