cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1654) EC2Snitch
Date Mon, 03 Jan 2011 21:09:47 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams updated CASSANDRA-1654:
----------------------------------------

    Attachment: 1654-v4.txt

v4 fixes the NPE caused by the node asking the snitch for its own dc/rack info, which of course
is not in gossip.

> 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-incomplete.txt, 1654-v2.txt, 1654-v4.txt,
1654.txt
>
>
> 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