cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Hermes (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1654) EC2Snitch
Date Wed, 27 Oct 2010 19:47:20 GMT

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

Jon Hermes updated CASSANDRA-1654:
----------------------------------

    Attachment: 1654.txt

$ bin/cassandra -f
...
 INFO 19:42:51,530 DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap
 *INFO 19:42:51,558 EC2Snitch using region: us-east, zone: 1c.*
 INFO 19:42:51,623 Creating new commitlog segment /var/lib/cassandra/commitlog/CommitLog-1288208571623.log
...

\o/


If the response code isn't 200 OK, then it flubs. If for some reason it does return a response,
the region/zone parsing logic will most likely fail. But if they run on ec2, It Just Works
(tm).

> 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.


Mime
View raw message