Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 27 Mar 2014 18:58:15 +0000 (UTC)
From: "Russ Hatch (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12704030.1395939473628.18898.1395946695232@arcas>
In-Reply-To: <JIRA.12704030.1395939473628@arcas>
References: <JIRA.12704030.1395939473628@arcas>
Subject: [jira] [Commented] (CASSANDRA-6943) very contentious writes result
 in performance degradation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Russ Hatch commented on CASSANDRA-6943:
---------------------------------------

not sure if it helps, but I forgot to mention that the stress commands were sent to node4.

> very contentious writes result in performance degradation
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-6943
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6943
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Russ Hatch
>         Attachments: node4_jstack.log, node5_jstack.log, node6_jstack.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)