However, it's good to determine *how* it failed. If nodetool just died or
timed out, that's no big deal, it'll finish.
On Mon, Jan 9, 2017 at 11:00 PM, Jonathan Haddad wrote:
> There's no downgrade procedure. You either upgrade or you go back to a
> snapshot from the previous version.
> On Mon,
There's no downgrade procedure. You either upgrade or you go back to a
snapshot from the previous version.
On Mon, Jan 9, 2017 at 8:13 PM Prakash Chauhan
wrote:
> Hi All ,
>
> Do we have an official procedure to rollback the upgrade of C* from 2.0.x
> to 2.1.x ?
>
>
> Description:
> I have upgrad
Hi All ,
Do we have an official procedure to rollback the upgrade of C* from 2.0.x to
2.1.x ?
Description:
I have upgraded C* from 2.0.x to 2.1.x . As a part of upgrade procedure , I
have to run nodetool upgradesstables .
What if the command fails in the middle ? Some of the sstables will be i
I'm not sure I understand the culmination of the past couple of threads on this.
With a situation like:
http://cassci.datastax.com/view/cassandra-3.11/job/cassandra-3.11_dtest/lastCompletedBuild/testReport/
We have some sense of stability on what might be flaky tests(?).
Again, I'm not sure what
