You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Mark Furlong <mf...@ancestry.com> on 2017/07/06 20:09:23 UTC
Repair on system_auth
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
mfurlong@ancestry.com<ma...@ancestry.com>
M: 801-859-7427
O: 801-705-7115
1300 W Traverse Pkwy
Lehi, UT 84043
[http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]
RE: Repair on system_auth
Posted by Mark Furlong <mf...@ancestry.com>.
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:fayhou@coupang.com]
Sent: Thursday, July 6, 2017 2:24 PM
To: User <us...@cassandra.apache.org>
Subject: Re: Repair on system_auth
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 <sb...@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 <mf...@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
mfurlong@ancestry.com<ma...@ancestry.com>
M: 801-859-7427
O: 801-705-7115
1300 W Traverse Pkwy
Lehi, UT 84043
[http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org<ma...@cassandra.apache.org>
For additional commands, e-mail: user-help@cassandra.apache.org<ma...@cassandra.apache.org>
Re: Repair on system_auth
Posted by Hannu Kröger <hk...@gmail.com>.
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] <fa...@coupang.com> 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 running repair job
>
>> On Thu, Jul 6, 2017 at 1:14 PM, Subroto Barua <sb...@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 <mf...@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
>>
>> mfurlong@ancestry.com
>> M: 801-859-7427
>>
>> O: 801-705-7115
>>
>> 1300 W Traverse Pkwy
>>
>> Lehi, UT 84043
>>
>>
>>
>>
>>
>> <image002.png>
>>
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: user-help@cassandra.apache.org
>
Re: Repair on system_auth
Posted by Fay,
,
Storage,
,
fa...@coupang.com.
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 <sb...@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 <
> mfurlong@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
>
> *mfurlong@ancestry.com <mf...@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-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
gossip down failure detected
Posted by Peng Xiao <25...@qq.com>.
Hi,
We are experiencing the following issue,the rt will fly to 15s sometime.and after adjusting the batch size,
it looks better,but still have the following issue.Could any one advise?
INFO [GossipTasks:1] 2017-07-07 08:56:33,410 Gossiper.java:1009 - InetAddress /172.16.xx.39 is now DOWN
on 172.16.xx.39,we can see the following log:
WARN [SharedPool-Worker-18] 2017-07-07 08:56:12,049 BatchStatement.java:255 - Batch of prepared statements for [ecommercedata.ecommerce_baitiao_reco
rd_by_order_no] is of size 9470, exceeding specified threshold of 5120 by 4350.
WARN [GossipTasks:1] 2017-07-07 08:56:44,052 FailureDetector.java:258 - Not marking nodes down due to local pause of 31835321522 > 5000000000
INFO [ScheduledTasks:1] 2017-07-07 08:56:44,055 MessagingService.java:929 - READ messages were dropped in last 5000 ms: 48 for internal timeout and
0 for cross node timeout
INFO [ScheduledTasks:1] 2017-07-07 08:56:44,055 MessagingService.java:929 - RANGE_SLICE messages were dropped in last 5000 ms: 12 for internal timeo
ut and 0 for cross node timeout
INFO [ScheduledTasks:1] 2017-07-07 08:56:44,055 StatusLogger.java:51 - Pool Name Active Pending Completed Blocked All T
ime Blocked
INFO [ScheduledTasks:1] 2017-07-07 08:56:44,056 StatusLogger.java:66 - MutationStage 7 1380 618231255 0
0
Thanks
Re: Repair on system_auth
Posted by Subroto Barua <sb...@yahoo.com.INVALID>.
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 <mf...@ancestry.com> wrote:
<!--#yiv8845031033 _filtered #yiv8845031033 {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv8845031033 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv8845031033 {font-family:"Bradley Hand ITC";panose-1:3 7 4 2 5 3 2 3 2 3;} _filtered #yiv8845031033 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered #yiv8845031033 {font-family:Verdana;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv8845031033 #yiv8845031033 p.yiv8845031033MsoNormal, #yiv8845031033 li.yiv8845031033MsoNormal, #yiv8845031033 div.yiv8845031033MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv8845031033 a:link, #yiv8845031033 span.yiv8845031033MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv8845031033 a:visited, #yiv8845031033 span.yiv8845031033MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv8845031033 span.yiv8845031033EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv8845031033 .yiv8845031033MsoChpDefault {font-family:"Calibri", sans-serif;} _filtered #yiv8845031033 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv8845031033 div.yiv8845031033WordSection1 {}-->
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
|
|
mfurlong@ancestry.com
M: 801-859-7427
O: 801-705-7115
1300 W Traverse Pkwy
Lehi, UT 84043
|
|
|
|
|
|