cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1654) EC2Snitch
Date Wed, 12 Jan 2011 19:42:48 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980878#action_12980878
] 

Hudson commented on CASSANDRA-1654:
-----------------------------------

Integrated in Cassandra-0.7 #154 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/154/])
    ec2 snitch.  Patch by Jon Hermes, Matt Dennis, and brandonwilliams.
Reviewed by brandonwilliams for CASSANDRA-1654


> EC2Snitch
> ---------
>
>                 Key: CASSANDRA-1654
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1654
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Brandon Williams
>             Fix For: 0.7.1
>
>         Attachments: 1654-cassandra-0.7-v3.txt, 1654-cassandra-0.7-v5.txt, 1654-incomplete.txt,
1654-v2.txt, 1654-v4.txt, 1654.txt
>
>   Original Estimate: 16h
>  Remaining Estimate: 16h
>
> This will be a snitch extending AbstractNetworkTopologySnitch that pulls DC from instance
metadata placement_availability_zone.
> I don't think we can get rack information so the choice is between picking something
unique-per-machine to be the rack or assigning everything in the DC the same rack.  Second
seems easier, so let's use placement_availability_zone for rack, too.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message