[
https://issues.apache.org/jira/browse/CASSANDRA-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111368#comment-14111368
]
Gregory Ramsperger commented on CASSANDRA-4026:
-----------------------------------------------
Not to reopen ancient tickets, but code was added in CASSANDRA-5897 to pull in
SnitchProperties. Would it not be desirable to address this by looking at an
additional property and choosing between legacy naming and a full, consistent
with other EC2 APIs, naming scheme?
Something similar to this commit
[https://github.com/ramsperger/cassandra/commit/bf1ee0251e5cf46b8af28282e22c4fbf29d85f33?w=1]?
> EC2 snitch incorrectly reports regions
> --------------------------------------
>
> Key: CASSANDRA-4026
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4026
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.8
> Environment: Ubuntu 10.10 64 bit Oracle Java 6
> Reporter: Todd Nine
> Assignee: Vijay
> Fix For: 1.0.9, 1.1.0
>
> Attachments: 0001-CASSANDRA-4026.patch
>
>
> Currently the org.apache.cassandra.locator.Ec2Snitch reports "us-west" in
> both the oregon and the california data centers. This is incorrect, since
> they are different regions.
> California => us-west-1
> Oregon => us-west-2
> wget http://169.254.169.254/latest/meta-data/placement/availability-zone
> returns the value "us-west-2a"
> After parsing this returns
> DC = us-west Rack = 2a
> What it should return
> DC = us-west-2 Rack = a
> This makes it possible to use multi region when both regions are in the west
> coast.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
