f the cluster in such a
> configuration, but I don’t think that it is related to this configuration,
> though it could be.
>
> Mitchell
>
> *From:* Peter Sanford [mailto:psanf...@retailnext.net
> ]
> *Sent:* Monday, June 09, 2014 7:19 AM
> *To:* user@cassandra.apache.
ilto:psanf...@retailnext.net]
> Sent: Monday, June 09, 2014 7:19 AM
> To: user@cassandra.apache.org
> Subject: Re: VPC AWS
>
> Your general assessments of the limitations of the Ec2 snitches seem to match
> what we've found. We're currently using the GossipingPropertyFi
with the performance of the cluster in such a
configuration, but I don’t think that it is related to this configuration,
though it could be.
Mitchell
From: Peter Sanford [mailto:psanf...@retailnext.net]
Sent: Monday, June 09, 2014 7:19 AM
To: user@cassandra.apache.org
Subject: Re: VPC AWS
Your
gt;> You can have a ring spread across EC2 and the public subnet of a VPC.
>>>> That is how we did our migration. In our case, we simply replaced the
>>>> existing EC2 node with a new instance in the public VPC, restored from a
>>>> backup taken right before the
backup taken right before the switch.
>>>
>>> -Mike
>>>
>>> ------
>>> *From:* Aiman Parvaiz
>>> *To:* Michael Theroux
>>> *Cc:* "user@cassandra.apache.org"
>>> *Sent:* Thursday, June
gt;>
>> --
>> *From:* Aiman Parvaiz
>> *To:* Michael Theroux
>> *Cc:* "user@cassandra.apache.org"
>> *Sent:* Thursday, June 5, 2014 2:39 PM
>> *Subject:* Re: VPC AWS
>>
>> Thanks for this info Michael. As
ublic VPC, restored from a
> backup taken right before the switch.
>
> -Mike
>
> --
> *From:* Aiman Parvaiz
> *To:* Michael Theroux
> *Cc:* "user@cassandra.apache.org"
> *Sent:* Thursday, June 5, 2014 2:39 PM
> *Subject:* Re: VP
From: Aiman Parvaiz
To: Michael Theroux
Cc: "user@cassandra.apache.org"
Sent: Thursday, June 5, 2014 2:39 PM
Subject: Re: VPC AWS
Thanks for this info Michael. As far as restoring node in public VPC is
concerned I was thinking ( and I might be wrong here) if we can have a ri
se, many
> of the moved nodes required slightly different configurations for items
> like the seeds.
>
> Its been a couple of years, so my memory on this maybe a little fuzzy :)
>
> -Mike
>
> --
> *From:* Aiman Parvaiz
> *To:* user@cassan
rs, so my memory on this maybe a little fuzzy :)
-Mike
From: Aiman Parvaiz
To: user@cassandra.apache.org; Michael Theroux
Sent: Thursday, June 5, 2014 12:55 PM
Subject: Re: VPC AWS
Michael,
Thanks for the response, I am about to head in to something very s
We personally use the EC2Snitch, however, we don't have the multi-region
requirements you do,
-Mike
From: Alain RODRIGUEZ
To: user@cassandra.apache.org
Sent: Thursday, June 5, 2014 9:14 AM
Subject: Re: VPC AWS
I think you can define VPC subnet
Well if you are talking about the transition I think we are going to do it
this way
- Existing cluster out of any VPC -> DC1
- New VPC cluster, with subnet private + public -> DC2
- Add / Rebuild DC2
- Switch clients from DC1 to DC2
- Remove DC1
- Switch client inside the VPC
- Remove public VPC s
A general thought, if you're using AWS for this, I'd strongly recommend you
consider using OpsWorks and custom chef recipes for your node deployment if
its an option for you. The easy of provisioning new nodes without the need
for snapshotting is certainly worth the hassle, and there are already
s
I was making assumptions (sorry!), namely the goal to switching to vpc
was getting "backend resources" (like cassandra) off the public internet.
Will
On Thursday, June 5, 2014, Alain RODRIGUEZ wrote:
> I think you can define VPC subnet to be public (to have public + private
> IPs) or private on
I think you can define VPC subnet to be public (to have public + private
IPs) or private only.
Any insight regarding snitches ? What snitch do you guys use ?
2014-06-05 15:06 GMT+02:00 William Oberman :
> I don't think traffic will flow between "classic" ec2 and vpc directly.
> There is some ki
I don't think traffic will flow between "classic" ec2 and vpc directly.
There is some kind of gateway bridge instance that sits between, acting as
a NAT. I would think that would cause new challenges for:
-transitions
-clients
Sorry this response isn't heavy on content! I'm curious how this thr
Hello Alain,
We switched from EC2 to VPC a couple of years ago. The process for us was
long, slow and multi step.
In our case, we don't need to consider multi-DC. However, in our
infrastructure we were rapidly running out of IP addresses, and wished to move
to VPC to give us a nearly inexhau
Hello Alain,
We switched from EC2 to VPC a couple of years ago. The process for us was
long, slow, and multi step for our (at the time) 6 node cluster.
In our case, we don't need to consider multi-DC. However, in our
infrastructure we were rapidly running out of IP addresses, and wished to mo
Using 2.0.x, we hit https://issues.apache.org/jira/browse/CASSANDRA-2380 when
deploying in a VPC.
We worked around this by adding a hostname in /etc/hosts.
Apart from that, nothing specific. We use only internal ip's, no public ip's
and no broadcast etc. It works very well.
/Johan
From: Alain
19 matches
Mail list logo
