[
https://issues.apache.org/jira/browse/CASSANDRA-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933802#comment-13933802
]
Russ Hatch commented on CASSANDRA-6848:
---------------------------------------
happens every time on my austin test cluster (stress-2.1 targeting various
versions)
happens more sporadically locally, but once it happens for a given cluster it
seems to happen every time.
I'm getting it to reproduce today with stress from 2.1, and a ccm cluster built
from 2.1. Happens using the stress counterwrite command I mentioned two
comments above this one.
> 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)
