cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-6848) stress (2.1) spams console with java.util.NoSuchElementException when run against nodes recently created
Date Wed, 12 Mar 2014 23:39:44 GMT

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

Benedict edited comment on CASSANDRA-6848 at 3/12/14 11:39 PM:
---------------------------------------------------------------

On a hunch, tried "-mode thrift" (i.e. with smart routing disabled) on the vague idea that
it might be grabbing the topology/endpoint data before the cluster is ready to deliver it
fully (or that maybe 2.0 can't). It fixes the problem.

So not sure exactly the cause, but it's probably not a major issue. If it's a race on cluster
startup, it's probably not a big deal, but if it's an inherent limitation with 2.0 we should
probably detect that and let the user know. Either way, should fail out more gracefully whatever
the case.


was (Author: benedict):
On a hunch, tried "-mode thrift" (i.e. with smart routing disabled) on the vague idea that
it might be grabbing the topology/endpoint data before the cluster is ready to deliver it
fully (or that maybe 2.0 can't). It fixes the problem.

So not sure exactly the cause, but it's probably not a major issue - something we should ideally
fail more gracefully with. If it's a race on cluster startup, it's probably not a big deal,
but if it's an inherent limitation with 2.0 we should probably detect that and let the user
know. Either way, should possibly fail out more gracefully whatever the case.

> 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'm trying to make performance comparisons between 2.1 and 2.0. To accomplish this I'm
using the new stress in 2.1, and running it against 2.0 nodes.
> I don't get any stack trace on the console, but I get two java.util.NoSuchElementException
for each operation stress is doing.
> The reproduce build a ccm cluster with the cassandra-2.0 branch . Run a simple stress
command from 2.1 like cassandra-stress write n=10 .



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message