You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/11/02 16:32:27 UTC
[jira] Commented: (CASSANDRA-1654) EC2Snitch
[ https://issues.apache.org/jira/browse/CASSANDRA-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927469#action_12927469 ]
Jonathan Ellis commented on CASSANDRA-1654:
-------------------------------------------
(imo the most straightforward way to spread dc+rack via gossip is to add a ApplicationState.LOCATION state.)
> 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: Jon Hermes
> Fix For: 0.7.0
>
> Attachments: 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.