[
https://issues.apache.org/jira/browse/CASSANDRA-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933804#comment-13933804
]
Russ Hatch commented on CASSANDRA-6848:
---------------------------------------
To add 2 cents to the discussion above, it will be a great help if we can
expect stress-2.1 to work against 2.0 clusters so we can make meaningful
comparisons between these versions (otherwise it's going to be apples to
oranges).
But I'm getting this to happen with stress-2.1 targeting a 2.1 cluster as well,
so I think version may have nothing to do with it (or maybe two different
problems are manifesting as the exceptions output to the console).
> 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
> Fix For: 2.1 beta2
>
>
> 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)
