cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4026) EC2 snitch incorrectly reports regions
Date Mon, 12 Mar 2012 18:18:38 GMT


Brandon Williams commented on CASSANDRA-4026:

bq. hence after recovery they will not be able to be recovered via repair

One replica will always be in the right spot so you can repair.

bq. BTW: The attached patch can break after we AWS has 24 AZ's which is highly unlikely but
i will create a ticket requesting for API for Regions instead of AZ.

That would be great.  Unfortunately when we have that, we'll still have to munge the name
(and rack names) to be backwards compatible :(

This ticket makes me sad, but +1.
> EC2 snitch incorrectly reports regions
> --------------------------------------
>                 Key: CASSANDRA-4026
>                 URL:
>             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
>         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 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message