You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2011/07/28 22:30:10 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 ]

Brandon Williams updated CASSANDRA-2452:
----------------------------------------

    Fix Version/s:     (was: 0.8.3)
                   1.0

> 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: 1.0
>
>         Attachments: 2452-EC2Snitch-Changes.txt, 2452-Ec2Multi-Region-v3.patch, 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