Nare Gasparyan created CASSANDRA-4407:
-----------------------------------------

             Summary: timout excpetion in client side and AssertionError in 
cassandra log
                 Key: CASSANDRA-4407
                 URL: https://issues.apache.org/jira/browse/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


Hello.

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(ExceptionsTranslatorImpl.java:42)
at 
me.prettyprint.cassandra.service.KeyspaceServiceImpl$11.execute(KeyspaceServiceImpl.java:432)
at 
me.prettyprint.cassandra.service.KeyspaceServiceImpl$11.execute(KeyspaceServiceImpl.java:416)
at 
me.prettyprint.cassandra.service.Operation.executeAndSetResult(Operation.java:103)

In cassandra system.log I get

ERROR [ReadStage:492] 2012-07-02 21:50:50,280 AbstractCassandraDaemon.java 
(line 139) Fatal exception in thread Thread[ReadStage:492,5,main]
java.lang.AssertionError: 820255506 vs 518814720
at 
org.apache.cassandra.io.util.MmappedSegmentedFile.floor(MmappedSegmentedFile.java:65)
at 
org.apache.cassandra.io.util.MmappedSegmentedFile.getSegment(MmappedSegmentedFile.java:80)
at 
org.apache.cassandra.io.sstable.SSTableReader.getFileDataInput(SSTableReader.java:830)

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

Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to