cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nare Gasparyan (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-4407) timout excpetion in client side and AssertionError in cassandra log
Date Tue, 03 Jul 2012 21:24:34 GMT
Nare Gasparyan created CASSANDRA-4407:

             Summary: timout excpetion in client side and AssertionError in cassandra log
                 Key: CASSANDRA-4407
             Project: Cassandra
          Issue Type: Bug
          Components: API, Core
    Affects Versions: 1.0.10, 1.0.8
         Environment: Debian linux
            Reporter: Nare Gasparyan
            Priority: Critical


I moved my cassandra from one sever to another. Cassandra's version on the first server was
1.0.8 on the new one it is 1.0.10. I moved also data by copying all files under /var/lib/cassandra/data/mykeyspace.
and now it seems to me that some data has been corrupted during migration as I get the following
exceptions when getting data for some keys.
In cassandra client I get

me.prettyprint.hector.api.exceptions.HTimedOutException: TimedOutException()
at me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(
at me.prettyprint.cassandra.service.KeyspaceServiceImpl$11.execute(
at me.prettyprint.cassandra.service.KeyspaceServiceImpl$11.execute(
at me.prettyprint.cassandra.service.Operation.executeAndSetResult(

In cassandra system.log I get

ERROR [ReadStage:492] 2012-07-02 21:50:50,280 (line 139) Fatal
exception in thread Thread[ReadStage:492,5,main]
java.lang.AssertionError: 820255506 vs 518814720

Is this really data corruption problem and how can I fix it?
I have only one node so nodetool repair won't help.


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message