cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4026) EC2 snitch incorrectly reports regions
Date Fri, 09 Mar 2012 00:01:57 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vijay updated CASSANDRA-4026:
-----------------------------

    Comment: was deleted

(was: I ran through it a while ago. But the problem is that we cannot change the settings
on the current live clusters which uses Ec2MultiregionSnitch or Ec2Snitch without taking a
downtime. (If we change EC2Snitch/Ec2Multiregion snitch, we also need to change the schema
for the existing cluster).

Option 1: Leave the existing snitch as it is and add a new snitch.
Option 2: Parse for us-west-1 as us-west and parse us-west-2 as us-west2, as us-west-2 is
fairly new it wont affect a lot of us?

Brandon, Thoughts?
)
    
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message