You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Vijay (JIRA)" <ji...@apache.org> on 2011/06/09 21:18:59 UTC

[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip and hence natively support for EC2 mult-region's.

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

Vijay updated CASSANDRA-2452:
-----------------------------

    Attachment: 2452-OutboundTCPConnection.patch
                2452-Ec2Multi-Region.patch

rebase to 2491,

Snitch will automatically set the public IP by querying the AWS API

Snitch will set the private IP as a Gossip application state.

Snitch implements IESCS and will reset the connection if it is within the same region to communicate via private IP.

Implements Ec2Snitch to inherit its functionality and extend it for Multi-Region.
 
Operational: All the nodes in this cluster needs to be able to (modify the Security group settings in AWS) communicate via Public IP's both within the region and to the other regions.

> New EC2 Snitch to use public ip and hence natively support for EC2 mult-region's.
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2452
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2452
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.8 beta 1
>         Environment: JVM
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 0.8.1
>
>         Attachments: 2452-EC2Snitch-Changes.txt, 2452-Ec2Multi-Region.patch, 2452-Intro-EC2MultiRegionSnitch-V2.txt, 2452-OutboundTCPConnection.patch
>
>
> Make cassandra talk identify itself using the public ip (To avoid any future conflicts of private ips).
> 1) Split the logic of identification vs listen Address in the code.
> 2) Move the logic to assign IP address to the node into EndPointSnitch.
> 3) Make EC2 Snitch query for its public ip and use it for identification.
> 4) Make EC2 snitch to use InetAddress.getLocal to listen to the private ip.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira