:00 Anuj Wadehra <anujw_2...@yahoo.co.in>:
> Thanks All !!
>
> Anuj
>
> On Mon, 25/4/16, Alain RODRIGUEZ <arodr...@gmail.com> wrote:
>
> Subject: Re: Upgrading to SSD
> To: user@cassandra.apache.org
> Date:
Thanks All !!
Anuj
On Mon, 25/4/16, Alain RODRIGUEZ <arodr...@gmail.com> wrote:
Subject: Re: Upgrading to SSD
To: user@cassandra.apache.org
Date: Monday, 25 April, 2016, 2:45 PM
Hi
Anuj, You could do the following instead
to minimize
Hi Anuj,
> You could do the following instead to minimize server downtime:
>
> 1. rsync while the server is running
> 2. rsync again to get any new files
> 3. shut server down
> 4. rsync for the 3rd time
>
5. change directory in yaml and start back up
>
+1
Here are some more details about that
You could do the following instead to minimize server downtime:
1. rsync while the server is running
2. rsync again to get any new files
3. shut server down
4. rsync for the 3rd time
5. change directory in yaml and start back up
On Sat, Apr 23, 2016 at 12:23 PM Clint Martin <
As long as you shut down the node before you start copying and moving stuff
around it shouldn't matter if you take backups or snapshots or whatever.
When you add the filesystem for the ssd will you be removing the existing
filesystem? Or will you be able to keep both filesystems mounted at the
Hi
We have a 3 node cluster of 2.0.14. We use Read/Write Qorum and RF is 3. We
want to move data and commitlog directory from a SATA HDD to SSD. We have
planned to do a rolling upgrade.
We plan to run repair -pr on all nodes to sync data upfront and then execute
following steps on each server
