cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8008) "Timed out waiting for timer thread" on large stress command
Date Wed, 01 Oct 2014 15:28:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154940#comment-14154940
] 

Ryan McGuire commented on CASSANDRA-8008:
-----------------------------------------

[~tjake] Can you shed any light on the stress side of this?

{code}
54331853  ,     90577,   90577,   90577,   90577,     2.2,     1.8,     2.8,     4.9,    86.0,
   87.8,  564.8,  0.00415,      0,       0,       0,       0,       0
54438736  ,    104791,  104791,  104791,  104791,     1.9,     1.8,     2.8,     5.3,    10.6,
   11.9,  565.8,  0.00415,      0,       0,       0,       0,       0
54463942  ,     88466,   77595,   77595,   77595,     2.6,     1.8,     3.1,     8.0,    83.7,
   84.4,  566.1,  0.00414,      0,       0,       0,       0,       0
java.lang.RuntimeException: Timed out waiting for a timer thread - seems one got stuck
	at org.apache.cassandra.stress.util.Timing.snap(Timing.java:83)
	at org.apache.cassandra.stress.util.Timing.snap(Timing.java:118)
	at org.apache.cassandra.stress.StressMetrics.update(StressMetrics.java:156)
	at org.apache.cassandra.stress.StressMetrics.access$300(StressMetrics.java:42)
	at org.apache.cassandra.stress.StressMetrics$2.run(StressMetrics.java:104)
	at java.lang.Thread.run(Thread.java:745)
{code}

> "Timed out waiting for timer thread" on large stress command
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-8008
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8008
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Shawn Kumar
>         Attachments: file.log, node1-2.log, node1.log, node2-2.log, node2.log, perftest.log
>
>
> I've been using cstar_perf to test a performance scenario and was able to reproduce this
error on a two node cluster with stock 2.1.0 while carrying out large stress writes (50M keys):
> {noformat}
> java.lang.RuntimeException: Timed out waiting for a timer thread - seems one got stuck
>         at org.apache.cassandra.stress.util.Timing.snap(Timing.java:83)
>         at org.apache.cassandra.stress.util.Timing.snap(Timing.java:118)
>         at org.apache.cassandra.stress.StressMetrics.update(StressMetrics.java:156)
>         at org.apache.cassandra.stress.StressMetrics.access$300(StressMetrics.java:42)
>         at org.apache.cassandra.stress.StressMetrics$2.run(StressMetrics.java:104)
>         at java.lang.Thread.run(Thread.java:745)
> {noformat}
> It looks like a similar error to that found in CASSANDRA-6943. I've also attached the
test log and thread dumps. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message