[
https://issues.apache.org/jira/browse/CASSANDRA-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932561#comment-13932561
]
Russ Hatch commented on CASSANDRA-6848:
---------------------------------------
I should also mention that stress does still report statistics to the console,
they are just buried in the error output. It would be helpful to know if the
errors are impacting the performance stats or if they can safely be ignored.
> 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
>
> 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)
