This repository has been archived by the owner on Mar 31, 2022. It is now read-only.
Loop on only 3 segments #127
Comments
Bj0rnen
pushed a commit
that referenced
this issue
Jul 3, 2017
Fix repair parallelism in cluster overview output, for schedules/runs…
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
Cassandra version: 2.0.10
3 Nodes.
I found that reaper happening all the time loop on only 3 segments: 1, 68 and 135.
Log:
INFO [2015-10-27 14:47:51,225] [dw-17 - POST /repair_run?tables=Standard1&clusterName=spotify&keyspace=Keyspace1&owner=aeljami&cause=manual+spreaper+run] c.s.r.s.SegmentGenerator -
Dividing token range [-9223372036854775808,-3074457345618258603) into 67 segments
INFO [2015-10-27 14:47:51,228] [dw-17 - POST /repair_run?tables=Standard1&clusterName=spotify&keyspace=Keyspace1&owner=aeljami&cause=manual+spreaper+run] c.s.r.s.SegmentGenerator -
Dividing token range [-3074457345618258603,3074457345618258602) into 67 segments
INFO [2015-10-27 14:47:51,230] [dw-17 - POST /repair_run?tables=Standard1&clusterName=spotify&keyspace=Keyspace1&owner=aeljami&cause=manual+spreaper+run] c.s.r.s.SegmentGenerator -
Dividing token range [3074457345618258602,-9223372036854775808) into 67 segments
-----Segment 1----
INFO [2015-10-27 14:47:51,462] [spotify:1:1] c.s.r.s.SegmentRunner - It is ok to repair segment '1' on repair run with id '1'
INFO [2015-10-27 14:47:51,468] [spotify:1:1] c.s.r.c.JmxProxy - Triggering repair of range (-9223372036854775808,-9131597190716917343] for keyspace "Keyspace1" on host 127.0.0.2, with repair parallelism SEQUENTIAL, in cluster with Cassandra version '2.0.10' (can use DATACENTER_AWARE 'false'), for column families: [Standard1]
INFO [2015-10-27 14:47:51,486] [spotify:1:1] c.s.r.s.SegmentRunner - Repair for segment 1 started, status wait will timeout in 1800000 millis
INFO [2015-10-27 14:47:51,488] [spotify:1:1] c.s.r.s.SegmentRunner - Repair command 1854 on segment 1 returned with state RUNNING
INFO [2015-10-27 14:47:51,489] [spotify:1:1] c.s.r.s.SegmentRunner - Repair command 1854 on segment 1 has been cancelled while running
INFO [2015-10-27 14:47:51,489] [spotify:1:1] c.s.r.s.SegmentRunner - Postponing segment 1
INFO [2015-10-27 14:47:51,489] [spotify:1:1] c.s.r.s.SegmentRunner - Aborting repair on segment with id 1 on coordinator 127.0.0.2
-----Segment 68----
INFO [2015-10-27 14:47:51,519] [spotify:1:68] c.s.r.s.SegmentRunner - It is ok to repair segment '68' on repair run with id '1'
INFO [2015-10-27 14:47:51,521] [spotify:1:68] c.s.r.c.JmxProxy - Triggering repair of range (-3074457345618258603,-2982682499480400138] for keyspace "Keyspace1" on host 127.0.0.3, with repair parallelism SEQUENTIAL, in cluster with Cassandra version '2.0.10' (can use DATACENTER_AWARE 'false'), for column families: [Standard1]
INFO [2015-10-27 14:47:51,523] [spotify:1:68] c.s.r.s.SegmentRunner - Repair for segment 68 started, status wait will timeout in 1800000 millis
INFO [2015-10-27 14:47:51,533] [spotify:1:68] c.s.r.s.SegmentRunner - Repair command 1855 on segment 68 returned with state RUNNING
INFO [2015-10-27 14:47:51,533] [spotify:1:68] c.s.r.s.SegmentRunner - Repair command 1855 on segment 68 has been cancelled while running
INFO [2015-10-27 14:47:51,533] [spotify:1:68] c.s.r.s.SegmentRunner - Postponing segment 68
INFO [2015-10-27 14:47:51,533] [spotify:1:68] c.s.r.s.SegmentRunner - Aborting repair on segment with id 68 on coordinator 127.0.0.3
-----Segment 135----
INFO [2015-10-27 14:48:21,548] [spotify:1:135] c.s.r.c.JmxProxy - Triggering repair of range (3074457345618258602,3166232191756117067] for keyspace "Keyspace1" on host 127.0.0.1, with repair parallelism SEQUENTIAL, in cluster with Cassandra version '2.0.10' (can use DATACENTER_AWARE 'false'), for column families: [Standard1]
INFO [2015-10-27 14:48:21,551] [spotify:1:135] c.s.r.s.SegmentRunner - Repair for segment 135 started, status wait will timeout in 1800000 millis
INFO [2015-10-27 14:48:21,560] [spotify:1:135] c.s.r.s.SegmentRunner - Repair command 1859 on segment 135 returned with state RUNNING
INFO [2015-10-27 14:48:21,560] [spotify:1:135] c.s.r.s.SegmentRunner - Repair command 1859 on segment 135 has been cancelled while running
INFO [2015-10-27 14:48:21,560] [spotify:1:135] c.s.r.s.SegmentRunner - Postponing segment 135
INFO [2015-10-27 14:48:21,561] [spotify:1:135] c.s.r.s.SegmentRunner - Aborting repair on segment with id 135 on coordinator 127.0.0.1
-----Segment 1----
INFO [2015-10-27 14:49:51,464] [spotify:1:1] c.s.r.c.JmxProxy - Triggering repair of range (-9223372036854775808,-9131597190716917343] for keyspace "Keyspace1" on host 127.0.0.2, with repair parallelism SEQUENTIAL, in cluster with Cassandra version '2.0.10' (can use DATACENTER_AWARE 'false'), for column families: [Standard1]
INFO [2015-10-27 14:49:51,465] [spotify:1:1] c.s.r.s.SegmentRunner - Repair for segment 1 started, status wait will timeout in 1800000 millis
INFO [2015-10-27 14:49:51,471] [spotify:1:1] c.s.r.s.SegmentRunner - Repair command 1866 on segment 1 returned with state RUNNING
INFO [2015-10-27 14:49:51,471] [spotify:1:1] c.s.r.s.SegmentRunner - Repair command 1866 on segment 1 has been cancelled while running
INFO [2015-10-27 14:49:51,471] [spotify:1:1] c.s.r.s.SegmentRunner - Postponing segment 1
INFO [2015-10-27 14:49:51,472] [spotify:1:1] c.s.r.s.SegmentRunner - Aborting repair on segment with id 1 on coordinator 127.0.0.2
-----Segment 68----
INFO [2015-10-27 14:49:51,500] [spotify:1:68] c.s.r.c.JmxProxy - Triggering repair of range (-3074457345618258603,-2982682499480400138] for keyspace "Keyspace1" on host 127.0.0.3, with repair parallelism SEQUENTIAL, in cluster with Cassandra version '2.0.10' (can use DATACENTER_AWARE 'false'), for column families: [Standard1]
INFO [2015-10-27 14:49:51,501] [spotify:1:68] c.s.r.s.SegmentRunner - Repair for segment 68 started, status wait will timeout in 1800000 millis
INFO [2015-10-27 14:49:51,508] [spotify:1:68] c.s.r.s.SegmentRunner - Repair command 1867 on segment 68 returned with state RUNNING
INFO [2015-10-27 14:49:51,509] [spotify:1:68] c.s.r.s.SegmentRunner - Repair command 1867 on segment 68 has been cancelled while running
INFO [2015-10-27 14:49:51,509] [spotify:1:68] c.s.r.s.SegmentRunner - Postponing segment 68
INFO [2015-10-27 14:49:51,509] [spotify:1:68] c.s.r.s.SegmentRunner - Aborting repair on segment with id 68 on coordinator 127.0.0.3
-----Segment 135----
INFO [2015-10-27 14:49:51,536] [spotify:1:135] c.s.r.c.JmxProxy - Triggering repair of range (3074457345618258602,3166232191756117067] for keyspace "Keyspace1" on host 127.0.0.1, with repair parallelism SEQUENTIAL, in cluster with Cassandra version '2.0.10' (can use DATACENTER_AWARE 'false'), for column families: [Standard1]
INFO [2015-10-27 14:49:51,538] [spotify:1:135] c.s.r.s.SegmentRunner - Repair for segment 135 started, status wait will timeout in 1800000 millis
INFO [2015-10-27 14:49:51,545] [spotify:1:135] c.s.r.s.SegmentRunner - Repair command 1868 on segment 135 returned with state RUNNING
INFO [2015-10-27 14:49:51,545] [spotify:1:135] c.s.r.s.SegmentRunner - Repair command 1868 on segment 135 has been cancelled while running
INFO [2015-10-27 14:49:51,545] [spotify:1:135] c.s.r.s.SegmentRunner - Postponing segment 135
INFO [2015-10-27 14:49:51,545] [spotify:1:135] c.s.r.s.SegmentRunner - Aborting repair on segment with id 135 on coordinator 127.0.0.1
endless, no other segments.....
Any Idea ?
Greets,
The text was updated successfully, but these errors were encountered: