[
https://issues.apache.org/jira/browse/CASSANDRA-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russ Hatch updated CASSANDRA-6848:
----------------------------------
Description:
I don't get any stack trace on the console, but I get two
java.util.NoSuchElementException for each operation stress is doing.
This seems to occur when stress is being run against a recently created node
(such as one from ccm).
To reproduce: create a ccm cluster, and run stress against it within a few
minutes . Run a simple stress command like cassandra-stress write n=10 .
was:
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 .
> stress (2.1) spams console with java.util.NoSuchElementException when run
> against nodes recently created
> --------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6848
> Project: Cassandra
> Issue Type: Bug
> Reporter: Russ Hatch
> Assignee: Benedict
>
> I don't get any stack trace on the console, but I get two
> java.util.NoSuchElementException for each operation stress is doing.
> This seems to occur when stress is being run against a recently created node
> (such as one from ccm).
> To reproduce: create a ccm cluster, and run stress against it within a few
> minutes . Run a simple stress command like cassandra-stress write n=10 .
--
This message was sent by Atlassian JIRA
(v6.2#6252)
