Also before you get started. Make sure:
1) no one attempts to change schema during the process
2) no one attempts to run a repair
3) no one attempts to join a node
4) no one attempts to remove/move nodes from the cluster
Each of these things trigger repair sessions and stream data which do not
Thanks Alain. This was extremely helpful, really grateful.
Aiman
On Dec 22, 2016, at 5:00 AM, Alain RODRIGUEZ
> wrote:
Hi,
Here are some thoughts:
running 1.2.18. I plan to upgrade them to 2.2.latest
Going 1 major release at the time is probably
Hi,
Here are some thoughts:
running 1.2.18. I plan to upgrade them to 2.2.latest
>
Going 1 major release at the time is probably the safest way to go indeed.
>1. Install 2.0.latest on one node at a time, start and wait for it to
>join the ring.
>2. Run upgradesstables on this
Hi everyone,
I have 2 C* DCs with 12 nodes in each running 1.2.18. I plan to upgrade them to
2.2.latest and wanted to run by you experts my plan.
1. Install 2.0.latest on one node at a time, start and wait for it to join
the ring.
2. Run upgradesstables on this node.
3. Repeat Step