ok, thanks, so I don't use the -pr option anymore (I used it on the
first node). It seems to take some time. running for 150minutes to
complete 7% ...
Cheers,
Michael
On 14.09.2017 15:40, Alexander Dejanovski wrote:
> There should be no migration needed, but if you have a lot of data,
> antic
There should be no migration needed, but if you have a lot of data,
anticompaction could take a while the first time. The only way to make that
fast would be to mark all sstables as repaired, and then start running
incremental repair every day or so to have small datasets to anticompact.
But all th
ok, I have restarted the cluster to stop all repairs.
There is no "migration" process to move to incremental repair in 3.11?
So I can start "nodetool repair -pr" node after node or just "nodetool
repair" on one node?
Cheers,
Michael
On 14.09.2017 10:47, Alexander Dejanovski wrote:
> Hi Micha
Hi Micha,
Are you running incremental repair ?
If so, then validation fails when 2 repair sessions are running at the same
time, with one anticompacting an SSTable and the other trying to run a
validation compaction on it.
If you check the logs of the nodes that is referred to in the "Validation
Hi,
I started a repair (7 nodes, C* 3.11) but at once I get an exception in
the log:
"RepairException: [# on keyspace/table, [],
Validation failed in /ip"
The started nodetool repair hangs (the whole day...), strace shows it's
waiting...
What's the reason for this excpetion and what to
