Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B52AA17ABD for ; Mon, 29 Sep 2014 17:58:35 +0000 (UTC) Received: (qmail 17233 invoked by uid 500); 29 Sep 2014 17:58:34 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 17164 invoked by uid 500); 29 Sep 2014 17:58:34 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 16950 invoked by uid 99); 29 Sep 2014 17:58:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2014 17:58:34 +0000 Date: Mon, 29 Sep 2014 17:58:34 +0000 (UTC) From: "Shawn Kumar (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Issue Comment Deleted] (CASSANDRA-8008) "Timed out waiting for timer thread" on large stress command MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Kumar updated CASSANDRA-8008: ----------------------------------- Comment: was deleted (was: Locally on single node of 2.1.0) > "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)