> I changed logging to debug level, but still nothing is logged.
> Again - any help will be appreciated.
There is nothing at the ERROR level on any machine ?
check nodetool compactionstats to see if a validation compaction is running,
the repair may be waiting on this.
check nodetool netstats
Update - I am still experiencing the above issues, but not all the time. I
was able to run repair (on this keyspace) from node 2 and from node 4, but
now a different keyspace hangs on these nodes, and I am still not able to
run repair on node 1. It seems random. I changed logging to debug level,
bu
Hi,
On AWS, we had a 2 node cluster with RF 2.
We added 2 more nodes, then changed RF to 3 on all our keyspaces.
Next step was to run nodetool repair, node by node.
(In the meantime, we found that we must use CL quorum, which is affecting
our application's performance).
Started with node 1, which
