Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <25121526.118251294088987606.JavaMail.jira@thor>
Date: Mon, 3 Jan 2011 16:09:47 -0500 (EST)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1654) EC2Snitch
In-Reply-To: <16530588.38831287809961488.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.