[
https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027096#comment-13027096
]
Vijay commented on CASSANDRA-2452:
----------------------------------
Jonathan, yes it overlaps... the idea is to set the private and public address
automatically via this patch.... In #2491 The broadcast address is just used
for identification similarly to getLocalID()... i think this patch is less
intrusive... but if we can commit the other patch i can port this to
automatically set the broadcast address...
> 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-Intro-EC2MultiRegionSnitch-V2.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
