Afternoon,
We are noticing nodetool repair processes are not completing after a weeks
worth of time, and have resulted in some Cassandra nodes having more than one
process running do to cron scheduled. We are also chasing some performance
degradation after upgrading all nodes to version 1.2.8
nodetool repair just triggers repair procedure. You can kill nodetool after
start, it doesn't change anything. To stop repair you have to use nodetool
stop VALIDATION|COMPACTION
Thank you,
Andrey
On Thu, Aug 8, 2013 at 1:00 PM, Andy Losey and...@addthis.com wrote:
Afternoon,
We are
But node might be streaming data as well, in that case only option is to
restart node that started streaming operation
Sent from my iPhone
On Aug 8, 2013, at 5:56 PM, Andrey Ilinykh ailin...@gmail.com wrote:
nodetool repair just triggers repair procedure. You can kill nodetool after
start,
