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 56D15106CE for ; Fri, 28 Mar 2014 13:41:20 +0000 (UTC) Received: (qmail 97424 invoked by uid 500); 28 Mar 2014 13:41:19 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 97224 invoked by uid 500); 28 Mar 2014 13:41:18 -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 97190 invoked by uid 99); 28 Mar 2014 13:41:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Mar 2014 13:41:16 +0000 Date: Fri, 28 Mar 2014 13:41:16 +0000 (UTC) From: "Benedict (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-6943) UpdateFunction.abortEarly can cause BTree.update to leave its Builder in a bad state, which affects future operations 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-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-6943: -------------------------------- Summary: UpdateFunction.abortEarly can cause BTree.update to leave its Builder in a bad state, which affects future operations (was: very contentious writes result in performance degradation) > UpdateFunction.abortEarly can cause BTree.update to leave its Builder in a bad state, which affects future operations > --------------------------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-6943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6943 > Project: Cassandra > Issue Type: Bug > Reporter: Russ Hatch > Fix For: 2.1 beta2 > > Attachments: 6943.2.txt, 6943.txt, node4.log, node4_jstack.log, node5.log, node5_jstack.log, node6.log, node6_jstack.log, node7.log, node7_jstack.log, screenshot.png, screenshot2.png, stress_jstack.log > > > Running performance scenarios I have seen this characteristic drop in performance happen several times. A similar effect was reproduced in another test cluster. Operations eventually come to a standstill. > !screenshot.png! > !screenshot2.png! -- This message was sent by Atlassian JIRA (v6.2#6252)