[ 
https://issues.apache.org/jira/browse/CASSANDRA-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925525#action_12925525
 ] 

Jon Hermes edited comment on CASSANDRA-1654 at 10/27/10 4:26 PM:
-----------------------------------------------------------------

$ 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 169.254.169.254 doesn't exist, then there will be a "No Route to Host" 
error. 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).

      was (Author: jhermes):
    $ 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
>
>         Attachments: 1654.txt
>
>
> 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.

Reply via email to