cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Hatch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6848) stress (2.1) spams console with java.util.NoSuchElementException when run against nodes recently created
Date Thu, 13 Mar 2014 01:39:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932765#comment-13932765
] 

Russ Hatch commented on CASSANDRA-6848:
---------------------------------------

on second thought this doesn't seem to be purely timing as I suggested in the description
above. I let my nodes wait for 10 minutes before sending stress commands and still got the
flood of NoSuchElementException's. This is the command that triggered the problem after a
10 minute wait:
{noformat}
'cassandra-stress counterwrite n=5000000 CL=ONE -key populate=1..10000 -col n=FIXED\(1\) -schema
replication\(factor=3\) -rate threads=50'
{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
>
> 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)

Mime
View raw message