[
https://issues.apache.org/jira/browse/CASSANDRA-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933890#comment-13933890
]
Russ Hatch commented on CASSANDRA-6848:
---------------------------------------
I was able to isolate this a little bit more. Looks like if the first stress
command I run is the 'counterwrite' above, then the cluster is no good for
running stress after that (for even just a simple write n=10). Seems like
there's some state being preserved by stress or the cluster since the outcome
of a previous command is having an impact on subsequent runs.
However, if I run a simple write test first (write n=10), then follow with my
counterwrite test the problem seems to go away.
> 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)
