Alain Rodriguez outlined this procedure that he was going to try, but failed to 
mention whether this actually worked :-)

https://mail-archives.apache.org/mod_mbox/incubator-cassandra-user/201406.mbox/%3cca+vsrlopop7th8nx20aoz3as75g2jrjm3ryx119deklynhq...@mail.gmail.com%3E

/Janne

On 8 Sep 2014, at 23:05, Oleg Dulin <oleg.du...@gmail.com> wrote:

> I get that, but if you read my opening post, I have an existing cluster in 
> EC2 classic that I have no idea how to move to VPC cleanly.
> 
> 
> On 2014-09-08 19:52:28 +0000, Bram Avontuur said:
> 
> I have setup Cassandra into VPC with the EC2Snitch and it works without 
> issues. I didn't need to do anything special to the configuration. I have 
> created instances in 2 availability zones, and it automatically
> picks it up as 2 different data racks. Just make sure your nodes can see each 
> other in the VPC, e.g. setup a security group that allows connections from 
> other nodes from the same group.
> 
> There should be no need to use public IP's if whatever talks to cassandra is 
> also within your VPC.
> 
> Hope this helps.
> Bram
> 
> 
> On Mon, Sep 8, 2014 at 3:34 PM, Oleg Dulin <oleg.du...@gmail.com> wrote:
> Dear Colleagues:
> 
> I need to move Cassandra from EC2 classic into VPC.
> 
> What I was thinking is that I can create a new data center within VPC and 
> rebuild it from my existing one (switching to vnodes while I am at it). 
> However, I don't understand how the ec2-snitch will deal with this.
> 
> Another idea I had was taking the ec2-snitch configuration and converting it 
> into a Property file snitch. But I still don't understand how to perform this 
> move since I need my newly created VPC instances to have public IPs -- 
> something I would like to avoid.
> 
> Any thoughts are appreciated.
> 
> Regards,
> Oleg
> 
> 
> 

Reply via email to