There is a bug on repair system_auth keyspace. We just skip the repair on system_auth. Yes. it is ok to kill the running repair job
On Thu, Jul 6, 2017 at 1:14 PM, Subroto Barua <sbarua...@yahoo.com.invalid> wrote: > you can check the status via nodetool netstats > to kill the repair job, restart the instance > > > On Thursday, July 6, 2017, 1:09:42 PM PDT, Mark Furlong < > mfurl...@ancestry.com> wrote: > > > I have started a repair on my system_auth keyspace. The repair has started > and the process shows as running with ps but am not seeing any CPU with > top. I’m also note seeing any antientropy sessions building merkle trees in > the log. Can I safely kill a repair and how? > > > > > > *Mark Furlong* > > Sr. Database Administrator > > *mfurl...@ancestry.com <mfurl...@ancestry.com>* > M: 801-859-7427 > > O: 801-705-7115 > > 1300 W Traverse Pkwy > > Lehi, UT 84043 > > > > > > [image: http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org >
