I’m currently on 2.1.12. Are you saying this bug exists on the current latest
version 3.0.14?
Thank you
Mark
801-705-7115 office
From: Fay Hou [Storage Service] [mailto:fay...@coupang.com]
Sent: Thursday, July 6, 2017 2:24 PM
To: User
Subject: Re: Repair on system_auth
There is a bug on
You can also stop repair using JMX without restarting. There are scripts to do
that.
Hannu
> On 6 Jul 2017, at 23.24, Fay Hou [Storage Service]
> wrote:
>
> There is a bug on repair system_auth keyspace. We just skip the repair on
> system_auth. Yes. it is ok to kill the run
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
wrote:
> you can check the status via nodetool netstats
> to kill the repair job, restart the instance
&g
you can check the status via nodetool netstatsto kill the repair job, restart
the instance
On Thursday, July 6, 2017, 1:09:42 PM PDT, Mark Furlong
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
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
