[jira] [Resolved] (CASSANDRA-8008) "Timed out waiting for timer thread" on large stress command

["T Jake Luciani (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

T Jake Luciani resolved CASSANDRA-8008.
---------------------------------------
    Resolution: Not a Problem

Ninja'd a better error message to indicate it's a heap/GC issue

> "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, Tools
>            Reporter: Shawn Kumar
>            Assignee: T Jake Luciani
>            Priority: Minor
>         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)