Re: How do you do automatic restacking of AWS instance for cassandra?

[John Wong]

My approach is the obvious taking a big outage window especially at work we
are using 1.2 and is using token range. I am generally a believer that (1)
patches should be applied, but (2) routinely we replace each host with a
new EC2, so (1) I know my infrastructure code (puppet/chef/ansible/salt
stack/whatever) doesn't just work on a 12-year old working EC2 (of course,
I am joking about EC2 been up for 12 years).

The other approach I have been meaning to try is simply taking one node out
at a time, and let the new node stream over (this has an issue with the IP
changed, but be careful).

But I think with the new versions of Cassandra, you can use vnode. I have
been meaning to also try just adding new vnode and gradually retiring the
older one. Does this approach sound like what people would do?

EBS is great, and generally performance is great (but please pick a
reasonable instance type appropriate for your workload, running on m3.large
is definitely not the way to go for production usually, just an example).

John

On Sun, May 28, 2017 at 1:59 PM, daemeon reiydelle 
wrote:

> This is in fact an interesting security practice that makes sense. It
> assumes the existing ami had security holes that WERE ALREADY exploited.
> See if you can negotiate moving the hdfs volumes to persistent storage. Fyi
> two major banks I have worked with did much the same, but as the storage
> was SAN (with VMware ) I was able to make adjustments to the ansible
> scripts (client was providing mobile banking solutions to the bank)
>
> I had another client using AWS, Chef, Terraform. I WAS NOT able to make
> this work in Chef. I can do it with Ansible, Terraform, AWS however.
>
> “All men dream, but not equally. Those who dream by night in the dusty
> recesses of their minds wake up in the day to find it was vanity, but the
> dreamers of the day are dangerous men, for they may act their dreams with
> open eyes, to make it possible.” — T.E. Lawrence
>
> sent from my mobile
> Daemeon Reiydelle
> skype daemeon.c.m.reiydelle
> USA 415.501.0198 <(415)%20501-0198>
>
> On May 28, 2017 1:25 AM, "Anthony Grasso" 
> wrote:
>
>> Hi Surbhi,
>>
>> Please see my comment inline below.
>>
>> On 28 May 2017 at 12:11, Jeff Jirsa  wrote:
>>
>>>
>>>
>>> On 2017-05-27 18:04 (-0700), Surbhi Gupta 
>>> wrote:
>>> > Thanks a lot for all of your reply.
>>> > Our requirement is :
>>> > Our company releases AMI almost every month where they have some or the
>>> > other security packages.
>>> > So as per our security team we need to move our cassandra cluster to
>>> the
>>> > new AMI .
>>> > As this process happens every month, we would like to automate the
>>> process .
>>> > Few points to consider here:
>>> >
>>> > 1. We are using ephemeral drives to store cassandra data
>>> > 2. We are on dse 4.8.x
>>> >
>>> > So currently to do the process, we pinup a new nodes with new DC name
>>> and
>>> > join that DC, alter the keyspace, do rebuild  and later alter the
>>> keyspace
>>> > again to remove the old DC .
>>> >
>>> > But all of this process is manually done as of now.
>>> >
>>> > So i wanted to understand , on AWS, how do you do above kind of task
>>> > automatically ?
>>>
>>>
>>> At a previous employer, they used M4 class instances with data on a
>>> dedicated EBS volumes, so we could swap AMIs / stop / start / adjust
>>> instances without having to deal with this. This worked reasonably well for
>>> their scale (which was petabytes of data).
>>>
>>
>> This is a really good option as it avoids streaming data to replace a
>> node which could potentially be quicker if dealing with large amounts of
>> data on each node.
>>
>>
>>>
>>> Other companies using ephemeral tend to be more willing to just
>>> terminate instances and replace them (-Dcassandra.replace_address). If you
>>> stop cassandra, then boot a replacement with 'replace_address' set, it'll
>>> take over for the stopped instance, including re-streaming all data (as
>>> best it can, subject to consistency level and repair status). This may be
>>> easier for you to script than switching your fleet to EBS, but it's not
>>> without risk.
>>>
>>
>> A quick note if you do decide to go down this path. If you are using
>> Cassandra version 2.x.x and above, the cassandra.replace_address_firs
>> t_boot can also be used. This option works once when Cassandra is first
>> started and the replacement node inserted into the cluster. After that, the
>> option is ignored for all subsequent restarts, where as
>> cassandra.replace_address needs to be removed from the *cassandra-env.sh*
>> file in order to restart the node. Restart behaviour aside, both options
>> operate in the same way to replace a node in the cluster.
>>
>>
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>>
>>>
>>

Re: How do you do automatic restacking of AWS instance for cassandra?

[daemeon reiydelle]

This is in fact an interesting security practice that makes sense. It
assumes the existing ami had security holes that WERE ALREADY exploited.
See if you can negotiate moving the hdfs volumes to persistent storage. Fyi
two major banks I have worked with did much the same, but as the storage
was SAN (with VMware ) I was able to make adjustments to the ansible
scripts (client was providing mobile banking solutions to the bank)

I had another client using AWS, Chef, Terraform. I WAS NOT able to make
this work in Chef. I can do it with Ansible, Terraform, AWS however.

“All men dream, but not equally. Those who dream by night in the dusty
recesses of their minds wake up in the day to find it was vanity, but the
dreamers of the day are dangerous men, for they may act their dreams with
open eyes, to make it possible.” — T.E. Lawrence

sent from my mobile
Daemeon Reiydelle
skype daemeon.c.m.reiydelle
USA 415.501.0198

On May 28, 2017 1:25 AM, "Anthony Grasso"  wrote:

> Hi Surbhi,
>
> Please see my comment inline below.
>
> On 28 May 2017 at 12:11, Jeff Jirsa  wrote:
>
>>
>>
>> On 2017-05-27 18:04 (-0700), Surbhi Gupta 
>> wrote:
>> > Thanks a lot for all of your reply.
>> > Our requirement is :
>> > Our company releases AMI almost every month where they have some or the
>> > other security packages.
>> > So as per our security team we need to move our cassandra cluster to the
>> > new AMI .
>> > As this process happens every month, we would like to automate the
>> process .
>> > Few points to consider here:
>> >
>> > 1. We are using ephemeral drives to store cassandra data
>> > 2. We are on dse 4.8.x
>> >
>> > So currently to do the process, we pinup a new nodes with new DC name
>> and
>> > join that DC, alter the keyspace, do rebuild  and later alter the
>> keyspace
>> > again to remove the old DC .
>> >
>> > But all of this process is manually done as of now.
>> >
>> > So i wanted to understand , on AWS, how do you do above kind of task
>> > automatically ?
>>
>>
>> At a previous employer, they used M4 class instances with data on a
>> dedicated EBS volumes, so we could swap AMIs / stop / start / adjust
>> instances without having to deal with this. This worked reasonably well for
>> their scale (which was petabytes of data).
>>
>
> This is a really good option as it avoids streaming data to replace a node
> which could potentially be quicker if dealing with large amounts of data on
> each node.
>
>
>>
>> Other companies using ephemeral tend to be more willing to just terminate
>> instances and replace them (-Dcassandra.replace_address). If you stop
>> cassandra, then boot a replacement with 'replace_address' set, it'll take
>> over for the stopped instance, including re-streaming all data (as best it
>> can, subject to consistency level and repair status). This may be easier
>> for you to script than switching your fleet to EBS, but it's not without
>> risk.
>>
>
> A quick note if you do decide to go down this path. If you are using
> Cassandra version 2.x.x and above, the cassandra.replace_address_firs
> t_boot can also be used. This option works once when Cassandra is first
> started and the replacement node inserted into the cluster. After that, the
> option is ignored for all subsequent restarts, where as
> cassandra.replace_address needs to be removed from the *cassandra-env.sh*
> file in order to restart the node. Restart behaviour aside, both options
> operate in the same way to replace a node in the cluster.
>
>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>
>>
>

Re: How do you do automatic restacking of AWS instance for cassandra?

[Anthony Grasso]

Hi Surbhi,

Please see my comment inline below.

On 28 May 2017 at 12:11, Jeff Jirsa  wrote:

>
>
> On 2017-05-27 18:04 (-0700), Surbhi Gupta 
> wrote:
> > Thanks a lot for all of your reply.
> > Our requirement is :
> > Our company releases AMI almost every month where they have some or the
> > other security packages.
> > So as per our security team we need to move our cassandra cluster to the
> > new AMI .
> > As this process happens every month, we would like to automate the
> process .
> > Few points to consider here:
> >
> > 1. We are using ephemeral drives to store cassandra data
> > 2. We are on dse 4.8.x
> >
> > So currently to do the process, we pinup a new nodes with new DC name and
> > join that DC, alter the keyspace, do rebuild  and later alter the
> keyspace
> > again to remove the old DC .
> >
> > But all of this process is manually done as of now.
> >
> > So i wanted to understand , on AWS, how do you do above kind of task
> > automatically ?
>
>
> At a previous employer, they used M4 class instances with data on a
> dedicated EBS volumes, so we could swap AMIs / stop / start / adjust
> instances without having to deal with this. This worked reasonably well for
> their scale (which was petabytes of data).
>

This is a really good option as it avoids streaming data to replace a node
which could potentially be quicker if dealing with large amounts of data on
each node.


>
> Other companies using ephemeral tend to be more willing to just terminate
> instances and replace them (-Dcassandra.replace_address). If you stop
> cassandra, then boot a replacement with 'replace_address' set, it'll take
> over for the stopped instance, including re-streaming all data (as best it
> can, subject to consistency level and repair status). This may be easier
> for you to script than switching your fleet to EBS, but it's not without
> risk.
>

A quick note if you do decide to go down this path. If you are using
Cassandra version 2.x.x and above, the cassandra.replace_address_first_boot
can also be used. This option works once when Cassandra is first started
and the replacement node inserted into the cluster. After that, the option
is ignored for all subsequent restarts, where as
cassandra.replace_address needs
to be removed from the *cassandra-env.sh* file in order to restart the
node. Restart behaviour aside, both options operate in the same way to
replace a node in the cluster.


>
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

Re: How do you do automatic restacking of AWS instance for cassandra?

[Jeff Jirsa]

I understand that, but I'm not sure your point.

If you used ebs, you could stop one instance at a time, swap out your OS drive 
via new AMI, and start it again attached to your existing data drive, and 
bounce a whole cluster in a rolling manner, perhaps 5 minutes per node.

If you don't want to change to EBS (a fair position), the approach you're using 
is reasonable, or you could swap one node at a time by replacing it. I'd 
probably use your method, but I'd write tooling so it wasn't entirely manual.

-- 
Jeff Jirsa


> On May 27, 2017, at 7:13 PM, Surbhi Gupta  wrote:
> 
> We get the new AMI release with the new OS updates and we are not allowed to 
> use the old AMI .
> 
> 
>> On Sat, May 27, 2017 at 7:11 PM Jeff Jirsa  wrote:
>> 
>> 
>> 
>> 
>> On 2017-05-27 18:04 (-0700), Surbhi Gupta  wrote:
>> 
>> > Thanks a lot for all of your reply.
>> 
>> > Our requirement is :
>> 
>> > Our company releases AMI almost every month where they have some or the
>> 
>> > other security packages.
>> 
>> > So as per our security team we need to move our cassandra cluster to the
>> 
>> > new AMI .
>> 
>> > As this process happens every month, we would like to automate the process 
>> > .
>> 
>> > Few points to consider here:
>> 
>> >
>> 
>> > 1. We are using ephemeral drives to store cassandra data
>> 
>> > 2. We are on dse 4.8.x
>> 
>> >
>> 
>> > So currently to do the process, we pinup a new nodes with new DC name and
>> 
>> > join that DC, alter the keyspace, do rebuild  and later alter the keyspace
>> 
>> > again to remove the old DC .
>> 
>> >
>> 
>> > But all of this process is manually done as of now.
>> 
>> >
>> 
>> > So i wanted to understand , on AWS, how do you do above kind of task
>> 
>> > automatically ?
>> 
>> 
>> 
>> 
>> 
>> At a previous employer, they used M4 class instances with data on a 
>> dedicated EBS volumes, so we could swap AMIs / stop / start / adjust 
>> instances without having to deal with this. This worked reasonably well for 
>> their scale (which was petabytes of data).
>> 
>> 
>> 
>> Other companies using ephemeral tend to be more willing to just terminate 
>> instances and replace them (-Dcassandra.replace_address). If you stop 
>> cassandra, then boot a replacement with 'replace_address' set, it'll take 
>> over for the stopped instance, including re-streaming all data (as best it 
>> can, subject to consistency level and repair status). This may be easier for 
>> you to script than switching your fleet to EBS, but it's not without risk.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -
>> 
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> 
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>> 
>> 
>> 

Re: How do you do automatic restacking of AWS instance for cassandra?

[Michael Shuler]

On 05/27/2017 09:13 PM, Surbhi Gupta wrote:
> We get the new AMI release with the new OS updates and we are not
> allowed to use the old AMI .

Neither of Jeff's suggestions use the old AMI - that was my suggestion :)

> On Sat, May 27, 2017 at 7:11 PM Jeff Jirsa  > wrote:
> 
> At a previous employer, they used M4 class instances with data on a
> dedicated EBS volumes, so we could swap AMIs / stop / start / adjust
> instances without having to deal with this. This worked reasonably
> well for their scale (which was petabytes of data).

This suggestion seems like a nice way to easily cycle out old AMIs to a
new AMI quickly, getting rid of any data migration. A one-time pain to
switch to EBS with many benfits, which lends itself to automation well.

> Other companies using ephemeral tend to be more willing to just
> terminate instances and replace them (-Dcassandra.replace_address).
> If you stop cassandra, then boot a replacement with
> 'replace_address' set, it'll take over for the stopped instance,
> including re-streaming all data (as best it can, subject to
> consistency level and repair status). This may be easier for you to
> script than switching your fleet to EBS, but it's not without risk.

This suggestion for ephemeral data disks also seems like a possibly more
manageable way to cycle out old AMIs to a new AMI via individual node
replacement. The rest of the cluster needs to be healthy, and it may
mean an almost continuous node replacement, depending on node count.
This is potentially a lot less overall cluster load, since one
replacement node is streaming at a time, instead of all the data
streaming to a new replacement DC. Easier to automate than a replacement
DC, perhaps, too.

-- 
Kind regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How do you do automatic restacking of AWS instance for cassandra?

[Surbhi Gupta]

We get the new AMI release with the new OS updates and we are not allowed
to use the old AMI .


On Sat, May 27, 2017 at 7:11 PM Jeff Jirsa  wrote:

>
>
>
>
> On 2017-05-27 18:04 (-0700), Surbhi Gupta 
> wrote:
>
> > Thanks a lot for all of your reply.
>
> > Our requirement is :
>
> > Our company releases AMI almost every month where they have some or the
>
> > other security packages.
>
> > So as per our security team we need to move our cassandra cluster to the
>
> > new AMI .
>
> > As this process happens every month, we would like to automate the
> process .
>
> > Few points to consider here:
>
> >
>
> > 1. We are using ephemeral drives to store cassandra data
>
> > 2. We are on dse 4.8.x
>
> >
>
> > So currently to do the process, we pinup a new nodes with new DC name and
>
> > join that DC, alter the keyspace, do rebuild  and later alter the
> keyspace
>
> > again to remove the old DC .
>
> >
>
> > But all of this process is manually done as of now.
>
> >
>
> > So i wanted to understand , on AWS, how do you do above kind of task
>
> > automatically ?
>
>
>
>
>
> At a previous employer, they used M4 class instances with data on a
> dedicated EBS volumes, so we could swap AMIs / stop / start / adjust
> instances without having to deal with this. This worked reasonably well for
> their scale (which was petabytes of data).
>
>
>
> Other companies using ephemeral tend to be more willing to just terminate
> instances and replace them (-Dcassandra.replace_address). If you stop
> cassandra, then boot a replacement with 'replace_address' set, it'll take
> over for the stopped instance, including re-streaming all data (as best it
> can, subject to consistency level and repair status). This may be easier
> for you to script than switching your fleet to EBS, but it's not without
> risk.
>
>
>
>
>
>
>
> -
>
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>
>
>

Re: How do you do automatic restacking of AWS instance for cassandra?

[Jeff Jirsa]

On 2017-05-27 18:04 (-0700), Surbhi Gupta  wrote: 
> Thanks a lot for all of your reply.
> Our requirement is :
> Our company releases AMI almost every month where they have some or the
> other security packages.
> So as per our security team we need to move our cassandra cluster to the
> new AMI .
> As this process happens every month, we would like to automate the process .
> Few points to consider here:
> 
> 1. We are using ephemeral drives to store cassandra data
> 2. We are on dse 4.8.x
> 
> So currently to do the process, we pinup a new nodes with new DC name and
> join that DC, alter the keyspace, do rebuild  and later alter the keyspace
> again to remove the old DC .
> 
> But all of this process is manually done as of now.
> 
> So i wanted to understand , on AWS, how do you do above kind of task
> automatically ?


At a previous employer, they used M4 class instances with data on a dedicated 
EBS volumes, so we could swap AMIs / stop / start / adjust instances without 
having to deal with this. This worked reasonably well for their scale (which 
was petabytes of data). 

Other companies using ephemeral tend to be more willing to just terminate 
instances and replace them (-Dcassandra.replace_address). If you stop 
cassandra, then boot a replacement with 'replace_address' set, it'll take over 
for the stopped instance, including re-streaming all data (as best it can, 
subject to consistency level and repair status). This may be easier for you to 
script than switching your fleet to EBS, but it's not without risk.



-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How do you do automatic restacking of AWS instance for cassandra?

[Michael Shuler]

Just OS security updates? This sounds far more complicated than a simple
`apt-get upgrade` or `yum update` every month. If there happens to be
new kernel that month, throw in a `reboot`, too. I'd argue that OS
updates should be done when needed, sometimes in a much faster cycle
than monthly, in order to prevent 29 days of possibly sitting vulnerable
to known exploits.

Your data migration process sounds generally reasonable, if that's what
you have to deal with policy-wise. Automate the steps you are taking
manually and loop over the new DC data consistency checks to verify
you're ready to cut off the old DC. As your data grows or shrinks, the
time to migration completion with change, so the validations need to be
solid.

This just sounds like a painful exercise to perform every month. At some
large data size, it's possible that a month may not be enough time to
complete. This is the sort of migration I would see as totally
reasonable for a complete OS major version upgrade, for example from
Ubuntu 16.04 to 18.04, when that new OS version has been prescribed by
the security policy writers, but not simple OS updates, in my opinion.

-- 
Kind regards,
Michael

On 05/27/2017 08:04 PM, Surbhi Gupta wrote:
> Thanks a lot for all of your reply.
> Our requirement is :
> Our company releases AMI almost every month where they have some or the
> other security packages.
> So as per our security team we need to move our cassandra cluster to the
> new AMI .
> As this process happens every month, we would like to automate the process .
> Few points to consider here:
> 
> 1. We are using ephemeral drives to store cassandra data
> 2. We are on dse 4.8.x 
> 
> So currently to do the process, we pinup a new nodes with new DC name
> and join that DC, alter the keyspace, do rebuild  and later alter the
> keyspace again to remove the old DC .
> 
> But all of this process is manually done as of now.
> 
> So i wanted to understand , on AWS, how do you do above kind of task
> automatically ?
> 
> Thanks
> Surbhi
> 
> 
> On 27 May 2017 at 16:11, Marc Selwan  > wrote:
> 
> Hi Surbhi,
> 
> The only time I've heard of restacking, it was a specific term a
> financial services company used internally to describe a security
> related procedure specific to them.
> 
> If this sounds like you/the company you work for, send me a PM
> because I don't believe I can share those details in a public
> mailing list outside of that organization.
> 
> Best,
> Marc
> 
> 
> On Thu, May 25, 2017, 11:22 AM daemeon reiydelle  > wrote:
> 
> What is restacking?
> 
> */
> /*
> *Daemeon C.M. Reiydelle
> USA (+1) 415.501.0198 
> London (+44) (0) 20 8144 9872 */
> *
> *//*
> *//*“All men dream, but not equally. Those who dream by night in
> the dusty recesses of their minds wake up in the day to find it
> was vanity, but the dreamers of the day are dangerous men, for
> they may act their dreams with open eyes, to make it possible.” 
> — T.E. Lawrence*/*/*
> 
> */*
> 
> On Thu, May 25, 2017 at 10:24 AM, Surbhi Gupta
> mailto:surbhi.gupt...@gmail.com>> wrote:
> 
> Hi,
> 
> Wanted to understand, how do you do automatic restacking of
> cassandra nodes on AWS?
> 
> Thanks
> Surbhi
> 
> 
> -- 
> Marc Selwan | DataStax | Solutions Engineer | (925) 413-7079
>  
> 
> 
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How do you do automatic restacking of AWS instance for cassandra?

[Surbhi Gupta]

Thanks a lot for all of your reply.
Our requirement is :
Our company releases AMI almost every month where they have some or the
other security packages.
So as per our security team we need to move our cassandra cluster to the
new AMI .
As this process happens every month, we would like to automate the process .
Few points to consider here:

1. We are using ephemeral drives to store cassandra data
2. We are on dse 4.8.x

So currently to do the process, we pinup a new nodes with new DC name and
join that DC, alter the keyspace, do rebuild  and later alter the keyspace
again to remove the old DC .

But all of this process is manually done as of now.

So i wanted to understand , on AWS, how do you do above kind of task
automatically ?

Thanks
Surbhi


On 27 May 2017 at 16:11, Marc Selwan  wrote:

> Hi Surbhi,
>
> The only time I've heard of restacking, it was a specific term a financial
> services company used internally to describe a security related procedure
> specific to them.
>
> If this sounds like you/the company you work for, send me a PM because I
> don't believe I can share those details in a public mailing list outside of
> that organization.
>
> Best,
> Marc
>
> On Thu, May 25, 2017, 11:22 AM daemeon reiydelle 
> wrote:
>
>> What is restacking?
>>
>>
>>
>>
>>
>> *Daemeon C.M. ReiydelleUSA (+1) 415.501.0198 <(415)%20501-0198>London
>> (+44) (0) 20 8144 9872 <+44%2020%208144%209872>*
>>
>>
>> *“All men dream, but not equally. Those who dream by night in the dusty
>> recesses of their minds wake up in the day to find it was vanity, but the
>> dreamers of the day are dangerous men, for they may act their dreams with
>> open eyes, to make it possible.” — T.E. Lawrence*
>>
>>
>> On Thu, May 25, 2017 at 10:24 AM, Surbhi Gupta 
>> wrote:
>>
>>> Hi,
>>>
>>> Wanted to understand, how do you do automatic restacking of cassandra
>>> nodes on AWS?
>>>
>>> Thanks
>>> Surbhi
>>>
>>
>> --
> Marc Selwan | DataStax | Solutions Engineer | (925) 413-7079
>
>
>

Re: How do you do automatic restacking of AWS instance for cassandra?

[Marc Selwan]

Hi Surbhi,

The only time I've heard of restacking, it was a specific term a financial
services company used internally to describe a security related procedure
specific to them.

If this sounds like you/the company you work for, send me a PM because I
don't believe I can share those details in a public mailing list outside of
that organization.

Best,
Marc

On Thu, May 25, 2017, 11:22 AM daemeon reiydelle  wrote:

> What is restacking?
>
>
>
>
>
> *Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*
>
>
> *“All men dream, but not equally. Those who dream by night in the dusty
> recesses of their minds wake up in the day to find it was vanity, but the
> dreamers of the day are dangerous men, for they may act their dreams with
> open eyes, to make it possible.” — T.E. Lawrence*
>
>
> On Thu, May 25, 2017 at 10:24 AM, Surbhi Gupta 
> wrote:
>
>> Hi,
>>
>> Wanted to understand, how do you do automatic restacking of cassandra
>> nodes on AWS?
>>
>> Thanks
>> Surbhi
>>
>
> --
Marc Selwan | DataStax | Solutions Engineer | (925) 413-7079

Re: How do you do automatic restacking of AWS instance for cassandra?

[daemeon reiydelle]

What is restacking?





*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*


*“All men dream, but not equally. Those who dream by night in the dusty
recesses of their minds wake up in the day to find it was vanity, but the
dreamers of the day are dangerous men, for they may act their dreams with
open eyes, to make it possible.” — T.E. Lawrence*


On Thu, May 25, 2017 at 10:24 AM, Surbhi Gupta 
wrote:

> Hi,
>
> Wanted to understand, how do you do automatic restacking of cassandra
> nodes on AWS?
>
> Thanks
> Surbhi
>

How do you do automatic restacking of AWS instance for cassandra?

[Surbhi Gupta]

Hi,

Wanted to understand, how do you do automatic restacking of cassandra nodes
on AWS?

Thanks
Surbhi