incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Can not repair
Date Thu, 21 Jul 2011 14:54:08 GMT
Hi all,
I can't get the repair in my production.
We are out since 6 months but before we did not perform any delete do we 
didn't need to run repair.
Now we are out since 2 weeks with a new version of our software that performs 
delete but we can not get the nodetool repair working,

The first problem I see in the log is a: 

ERROR 16:34:49,790 Fatal exception in thread Thread[CompactionExecutor:1,1,
main] Keys must be written in ascending order.
        at org.apache.cassandra.db.CompactionManager.doCompaction
        at org.apache.cassandra.db.CompactionManager$
        at org.apache.cassandra.db.CompactionManager$
        at java.util.concurrent.FutureTask$Sync.innerRun(
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
        at java.util.concurrent.ThreadPoolExecutor$
(ThreadPoolExecutor .java:908)

I've read something concerning a change of the partitioner but I've never 
modified it. There is to say that we were online with 0.6.5 and now we are with 
0.7.5: to migrate from this version to another we followed the documentation 
(conversion of the yaml, nodetool drain and so on) ... 

The system is working even if there is this "problem" but not the repair. The 
limit of FD of the user running the repair is unlimited but everytime we get a 
"Too many open files".

I'm little bit worried cause if some delete reappears the webapp will export 
wrong data ...

Best regards


View raw message