[
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)
