[
https://issues.apache.org/jira/browse/CASSANDRA-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933944#comment-13933944
]
Russ Hatch commented on CASSANDRA-6848:
---------------------------------------
here's the exception printed from your branch with verbose logging:
{noformat}
java.util.NoSuchElementException
at
com.google.common.collect.AbstractIndexedListIterator.next(AbstractIndexedListIterator.java:82)
at
org.apache.cassandra.stress.util.SmartThriftClient.get(SmartThriftClient.java:117)
at
org.apache.cassandra.stress.util.SmartThriftClient.batch_mutate(SmartThriftClient.java:137)
at
org.apache.cassandra.stress.operations.ThriftCounterAdder$1.run(ThriftCounterAdder.java:77)
at
org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:251)
at
org.apache.cassandra.stress.operations.ThriftCounterAdder.run(ThriftCounterAdder.java:72)
at
org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:304)
{noformat}
> 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)
