[
https://issues.apache.org/jira/browse/CASSANDRA-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924824#action_12924824
]
Jonathan Ellis commented on CASSANDRA-1654:
-------------------------------------------
No, you should introspect it from the instance metadata.
http://docs.amazonwebservices.com/AmazonEC2/dg/2007-01-03/AESDG-chapter-instancedata.html
I think this will require the nodes to announce their DC/zone 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: Jon Hermes
> Fix For: 0.7.1
>
>
> 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.
