The error which keeps it from starting is below.
The files like
"mc_txn_anticompactionafterrepair_19a46410-459f-11e7-91c7-4f4e8666b5c8.log"
are on both disks of a node but are different .
Of course, just renaming (deleting) the two files (or making them equal)
makes cassandra start again. But I wo
On Wed, May 31, 2017 at 9:11 AM, Micha wrote:
> Hi,
>
> after failed repair on a three node cluster all nodes were down.
>
To clarify, was it failed repair that brought the nodes down so that you
had to start them back? Do you see any error messages or stack trace in
the logs?
> It cannot sta
Hi,
after failed repair on a three node cluster all nodes were down.
It cannot start, since it finds a mismatch in a
mc_txn_anticompactionafterrepair log file:
"got ADD "
"expected "ADD:..."
The two log files are different:
one has "ADD, ADD; REMOVE, REMOVE, COMMIT"
the other is missing an "
