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/04/11 22:01:07 UTC
[jira] [Created] (CASSANDRA-2452) EC2 Snitch to friendly to public
ip and natively support for EC2 mult-region.
EC2 Snitch to friendly to public ip and natively support for EC2 mult-region.
-----------------------------------------------------------------------------
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
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
[jira] [Commented] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026021#comment-13026021 ]
Jonathan Ellis commented on CASSANDRA-2452:
-------------------------------------------
what's the purpose of the new getLocalID / getListernAddress api?
Is there overlap here with CASSANDRA-2491?
> 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.0
>
> 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
[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-2452:
-----------------------------
Attachment: 2452-Ec2Multi-Region-v3.patch
> 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.2
>
> 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
[jira] [Commented] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072532#comment-13072532 ]
Hudson commented on CASSANDRA-2452:
-----------------------------------
Integrated in Cassandra #981 (See [https://builds.apache.org/job/Cassandra/981/])
Ec2 snitch with support for multiple regions.
Patch by Vijay Parthasarathy, reviewed by brandonwilliams for
CASSANDRA-2452
brandonwilliams : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151990
Files :
* /cassandra/trunk/src/java/org/apache/cassandra/gms/ApplicationState.java
* /cassandra/trunk/src/java/org/apache/cassandra/net/OutboundTcpConnectionPool.java
* /cassandra/trunk/src/java/org/apache/cassandra/locator/Ec2MultiRegionSnitch.java
* /cassandra/trunk/src/java/org/apache/cassandra/gms/VersionedValue.java
* /cassandra/trunk/src/java/org/apache/cassandra/net/OutboundTcpConnection.java
> 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
[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-2452:
-----------------------------
Attachment: (was: 2452-Ec2Multi-Region-v3.patch)
> 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.2
>
> 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
[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2452:
--------------------------------------
Reviewer: brandon.williams
Fix Version/s: 0.8
Issue Type: New Feature (was: Improvement)
Summary: New EC2 Snitch to use public ip and hence natively support for EC2 mult-region's. (was: Modify EC2 Snitch to use public ip and hence natively support for EC2 mult-region's.)
> 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
> Environment: JVM
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 0.8
>
> 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
[jira] [Commented] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072519#comment-13072519 ]
Vijay commented on CASSANDRA-2452:
----------------------------------
Awesome thanks brandon.... Cant wait for 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
[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-2452:
-----------------------------
Attachment: 2452-Ec2Multi-Region-v3.rtf
Changes made as per changes @ 2491...
> 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.2
>
> Attachments: 2452-EC2Snitch-Changes.txt, 2452-Ec2Multi-Region-v3.rtf, 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
[jira] [Updated] (CASSANDRA-2452) Modify EC2 Snitch to use public
ip and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-2452:
-----------------------------
Summary: Modify EC2 Snitch to use public ip and hence natively support for EC2 mult-region's. (was: EC2 Snitch to friendly to public ip and natively support for EC2 mult-region.)
> 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
>
> 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
[jira] [Commented] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-2452) Modify EC2 Snitch to use public
ip and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-2452:
-----------------------------
Attachment: 2452-Intro-EC2MultiRegionSnitch-V2.txt
V2 with the recommended way... Thanks!
> 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, 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
[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-2452:
-----------------------------
Attachment: 2452-Ec2Multi-Region-v3.patch
> 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.2
>
> 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
[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-2452) Modify EC2 Snitch to use public
ip and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-2452) New EC2 Snitch to use public ip
and hence natively support for EC2 mult-region's.
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-2452:
-----------------------------
Attachment: (was: 2452-Ec2Multi-Region-v3.rtf)
> 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.2
>
> 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
[jira] [Commented] (CASSANDRA-2452) Modify EC2 Snitch to use public
ip and hence natively support for EC2 mult-region's.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018821#comment-13018821 ]
Jonathan Ellis commented on CASSANDRA-2452:
-------------------------------------------
Is this a one-size-fits-all solution? It seems to me some people would prefer to continue to use the private interface. Maybe this should be a new snitch class.
> 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