cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-7068) AssertionError when running putget_test
Date Tue, 22 Apr 2014 18:32:14 GMT
Ryan McGuire created CASSANDRA-7068:

             Summary: AssertionError when running putget_test
                 Key: CASSANDRA-7068
             Project: Cassandra
          Issue Type: Bug
            Reporter: Ryan McGuire
            Assignee: Aleksey Yeschenko

running the putget_test like so:

nosetests2 -x -s -v

Yields this error in the logs on cassandra-2.0:

ERROR [Thrift:1] 2014-04-22 14:25:37,584 (line 198) Exception in thread
        at org.apache.cassandra.service.StorageProxy.sendToHintedEndpoints(
        at org.apache.cassandra.service.StorageProxy$2.apply(
        at org.apache.cassandra.service.StorageProxy.performWrite(
        at org.apache.cassandra.service.StorageProxy.mutate(
        at org.apache.cassandra.service.StorageProxy.mutateWithTriggers(
        at org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(
        at org.apache.cassandra.cql3.statements.ModificationStatement.execute(
        at org.apache.cassandra.cql3.QueryProcessor.processStatement(
        at org.apache.cassandra.cql3.QueryProcessor.process(
        at org.apache.cassandra.thrift.CassandraServer.execute_cql3_query(
        at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(
        at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(
        at org.apache.thrift.ProcessFunction.process(
        at org.apache.thrift.TBaseProcessor.process(
        at org.apache.cassandra.thrift.CustomTThreadPoolServer$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

On cassandra-2.1 I don't get any errors in the logs, but the test doesn't run , instead I
get a 'TSocket read 0 bytes' error. 

Test on 1.2 is fine.

After bisecting, it appears that a common commit 3a73e392fa424bff5378d4bb72117cfa28f9b0b7
is the cause.

This message was sent by Atlassian JIRA

View raw message