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 6C9D410D4D for ; Wed, 12 Mar 2014 23:29:54 +0000 (UTC) Received: (qmail 30976 invoked by uid 500); 12 Mar 2014 23:29:48 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 30882 invoked by uid 500); 12 Mar 2014 23:29:46 -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 30673 invoked by uid 99); 12 Mar 2014 23:29:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Mar 2014 23:29:45 +0000 Date: Wed, 12 Mar 2014 23:29:45 +0000 (UTC) From: "Benedict (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6848) stress (2.1) spams console with java.util.NoSuchElementException when run against earlier versions 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-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932648#comment-13932648 ] Benedict commented on CASSANDRA-6848: ------------------------------------- A quick update: Russ can only reproduce on one cluster, and I cannot reproduce locally, so going to introduce CASSANDRA-6849 as it seems the easiest way to track it down, and it's likely to be helpful in future anyway. No need to worry about backwards compatibility. I've used it on 2.0 plenty, it definitely _can_ work. We'll figure out why it isn't here. > stress (2.1) spams console with java.util.NoSuchElementException when run against earlier versions > -------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-6848 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6848 > Project: Cassandra > Issue Type: Bug > Reporter: Russ Hatch > Assignee: Benedict > > I'm trying to make performance comparisons between 2.1 and 2.0. To accomplish this I'm using the new stress in 2.1, and running it against 2.0 nodes. > I don't get any stack trace on the console, but I get two java.util.NoSuchElementException for each operation stress is doing. > The reproduce build a ccm cluster with the cassandra-2.0 branch . Run a simple stress command from 2.1 like cassandra-stress write n=10 . -- This message was sent by Atlassian JIRA (v6.2#6252)