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 D2A0E10A4E for ; Mon, 17 Mar 2014 08:33:08 +0000 (UTC) Received: (qmail 51534 invoked by uid 500); 17 Mar 2014 08:33:04 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 51448 invoked by uid 500); 17 Mar 2014 08:33:00 -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 51178 invoked by uid 99); 17 Mar 2014 08:32:47 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2014 08:32:47 +0000 Date: Mon, 17 Mar 2014 08:32:47 +0000 (UTC) From: "Marcus Eriksson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CASSANDRA-6774) Cleanup fails with assertion error after stopping previous run 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-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937541#comment-13937541 ] Marcus Eriksson edited comment on CASSANDRA-6774 at 3/17/14 8:31 AM: --------------------------------------------------------------------- hmm, i actually think we should throw an exception if we fail, so that the nodetool user gets some feedback without having to check logs, attached was (Author: krummas): hmm, i think we should throw an exception if we fail, so that the nodetool user gets some feedback without having to check logs, attached > Cleanup fails with assertion error after stopping previous run > -------------------------------------------------------------- > > Key: CASSANDRA-6774 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6774 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: 2.0.5 > Reporter: Keith Wright > Assignee: Marcus Eriksson > Fix For: 2.0.7 > > Attachments: 0001-6774-wip.patch, 0001-Dont-continue-after-failing-to-cancel-in-progress-co.patch, 6774-v2.txt > > > I am stress testing a new 2.0.5 cluster and did the following: > - start decommission during heavy write, moderate read load > - trigger cleanup on non-decommissioning node (nodetool cleanup) > - Started to see higher GC load stop stopped cleanup via nodetool stop CLEANUP > - attempt to launch cleanup now fails with the following message in console. > Cassandra log shows: http://aep.appspot.com/display/cKmlMcDuKD72iYAcBykDuVZkRWY/ -- This message was sent by Atlassian JIRA (v6.2#6252)