On Wed, May 31, 2017 at 9:11 AM, Micha <mich...@fantasymail.de> 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 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 "ADD" > I assume this is about commit log. There doesn't seem to be a separate log file named "mc_txn_anticompactionafterrepair" in your Cassandra version. Each of the nodes give this error. > > sstableutil -c also gives this error. > > How to deal with this? > I would try removing the faulty commit log file(s) and try to start the node again, until it works. This might mean that you'll have to remove all commit logs, but it's better than being completely down, I assume. -- Oleksandr "Alex" Shulgin | Database Engineer | Zalando SE | Tel: +49 176 127-59-707
