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
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
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.
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
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
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
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
Hi all,
We use Cassandra as a primary operational database in our data platform.
One of the cases - store the latest user profiles information that is
sourced from the upstream system. Importantly, we get each time the entire
row, not particular columns that were updated.
The access pattern is