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

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

    Attachment: 2452-EC2Snitch-Changes.txt

EC2Snitch and changes to make the IP Address identification more cleaner and 
controlled by the snitch which implements it. Tested and it works well..
 
There will be a separate follow-up patch to make nodes internally talk in local 
and public EC2 ip's as needed.

> Modify 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: Improvement
>          Components: Core
>    Affects Versions: 0.8
>         Environment: JVM
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>         Attachments: 2452-EC2Snitch-Changes.txt
>
>
> 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

Reply via email to