cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6097) nodetool repair randomly hangs.
Date Wed, 09 Oct 2013 14:48:55 GMT


Sylvain Lebresne commented on CASSANDRA-6097:

I've tried reproducing but lost patience when it didn't reproduce after > 1K iterations,
so can't say I've "tested" the fix, but the JMX documentation makes it pretty clear we should
handle those notifications and that it's very likely the source of the problem here. A few
minor nits on the patch though:
* Is there a reason JMXConnectionNotification.FAILED is not handled? Feels like it would be
a good to catch it too just in case.
* May want to mention in the error message for CLOSED/FAILED that we're not starting repair
for the other keyspaces not yet started.

But lgtm otherwise

> nodetool repair randomly hangs.
> -------------------------------
>                 Key: CASSANDRA-6097
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: DataStax AMI
>            Reporter: J.B. Langston
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 1.2.11
>         Attachments: 6097-1.2.txt, dse.stack, nodetool.stack
> nodetool repair randomly hangs. This is not the same issue where repair hangs if a stream
is disrupted. This can be reproduced on a single-node cluster where no streaming takes place,
so I think this may be a JMX connection or timeout issue. Thread dumps show that nodetool
is waiting on a JMX response and there are no repair-related threads running in Cassandra.
Nodetool main thread waiting for JMX response:
> {code}
> "main" prio=5 tid=7ffa4b001800 nid=0x10aedf000 in Object.wait() [10aede000]
>    java.lang.Thread.State: WAITING (on object monitor)
> 	at java.lang.Object.wait(Native Method)
> 	- waiting on <7f90d62e8> (a org.apache.cassandra.utils.SimpleCondition)
> 	at java.lang.Object.wait(
> 	at org.apache.cassandra.utils.SimpleCondition.await(
> 	- locked <7f90d62e8> (a org.apache.cassandra.utils.SimpleCondition)
> 	at
> 	at
> 	at
> 	at
> {code}
> When nodetool hangs, it does not print out the following message:
> "Starting repair command #XX, repairing 1 ranges for keyspace XXX"
> However, Cassandra logs that repair in system.log:
> 1380033480.95  INFO [Thread-154] 10:38:00,882 Starting repair command #X, repairing X
ranges for keyspace XXX
> This suggests that the repair command was received by Cassandra but the connection then
failed and nodetool didn't receive a response.
> Obviously, running repair on a single-node cluster is pointless but it's the easiest
way to demonstrate this problem. The customer who reported this has also seen the issue on
his real multi-node cluster.
> Steps to reproduce:
> Note: I reproduced this once on the official DataStax AMI with DSE 3.1.3 (Cassandra 1.2.6+patches).
 I was unable to reproduce on my Mac using the same version, and subsequent attempts to reproduce
it on the AMI were unsuccessful. The customer says he is able is able to reliably reproduce
on his Mac using DSE 3.1.3 and occasionally reproduce it on his real cluster. 
> 1) Deploy an AMI using the DataStax AMI at
> 2) Create a test keyspace
> {code}
> create keyspace test WITH replication = {'class': 'SimpleStrategy', 'replication_factor':
> {code}
> 3) Run an endless loop that runs nodetool repair repeatedly:
> {code}
> while true; do nodetool repair -pr test; done
> {code}
> 4) Wait until repair hangs. It may take many tries; the behavior is random.

This message was sent by Atlassian JIRA

View raw message