cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Boudreault (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-8316) "Did not get positive replies from all endpoints" error on incremental repair
Date Sun, 14 Dec 2014 21:58:14 GMT


Alan Boudreault updated CASSANDRA-8316:
    Attachment: CassandraDaemon-2014-12-14.snapshot.tar.gz

[~krummas], unfortunately, I'm still getting the same issue introduced on multiple nodes with
the v2 patch + CASSANDRA-8458. 8 nodes cluster and cassandra-stress with n=1000000

aboudreault@kovarro:~/dev/cstar/8316$ ccm node3 nodetool -- repair -par -inc 
[2014-12-14 16:30:48,037] Starting repair command #1, repairing 3 ranges for keyspace r1 (parallelism=PARALLEL,
[2014-12-14 16:30:48,040] Repair failed with error Already repairing SSTableReader(path='/home/aboudreault/.ccm/local/node3/data/r1/Standard1-d11383e083d411e4869ab56034537865/r1-Standard1-ka-38-Data.db'),
can not continue.

In addition, I  noticed that it took 20 minutes restart my cluster this time. Not sure if
it's related to this issue but I've attached a yourkit snapshot.

Let me know if I can anything else.

>  "Did not get positive replies from all endpoints" error on incremental repair
> ------------------------------------------------------------------------------
>                 Key: CASSANDRA-8316
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: cassandra 2.1.2
>            Reporter: Loic Lambiel
>            Assignee: Marcus Eriksson
>             Fix For: 2.1.3
>         Attachments: 0001-patch.patch, 8316-v2.patch, CassandraDaemon-2014-11-25-2.snapshot.tar.gz,
> Hi,
> I've got an issue with incremental repairs on our production 15 nodes 2.1.2 (new cluster,
not yet loaded, RF=3)
> After having successfully performed an incremental repair (-par -inc) on 3 nodes, I started
receiving "Repair failed with error Did not get positive replies from all endpoints." from
nodetool on all remaining nodes :
> [2014-11-14 09:12:36,488] Starting repair command #3, repairing 108 ranges for keyspace
xxxx (seq=false, full=false)
> [2014-11-14 09:12:47,919] Repair failed with error Did not get positive replies from
all endpoints.
> All the nodes are up and running and the local system log shows that the repair commands
got started and that's it.
> I've also noticed that soon after the repair, several nodes started having more cpu load
indefinitely without any particular reason (no tasks / queries, nothing in the logs). I then
restarted C* on these nodes and retried the repair on several nodes, which were successful
until facing the issue again.
> I tried to repro on our 3 nodes preproduction cluster without success
> It looks like I'm not the only one having this issue:
> Any idea?
> Thanks
> Loic

This message was sent by Atlassian JIRA

View raw message