incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Doubleday <daniel.double...@gmx.net>
Subject Re: Can not repair
Date Thu, 21 Jul 2011 16:02:48 GMT
Sounds like this one:

http://comments.gmane.org/gmane.comp.db.cassandra.user/15828

or

http://comments.gmane.org/gmane.comp.db.cassandra.user/15936

Hope you have a backup. That would make your life much easier ...


On Jul 21, 2011, at 4:54 PM, cbertu81@libero.it wrote:

> 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]
> java.io.IOException: Keys must be written in ascending order.
>        at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend
> (SSTableWriter.java:111)
>        at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.
> java:128)
>        at org.apache.cassandra.db.CompactionManager.doCompaction
> (CompactionManager.java:451)
>        at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.
> java:124)
>        at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.
> java:94)
>        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:886)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor .java:908)
>        at java.lang.Thread.run(Thread.java:662)
> 
> 
> 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
> 
> Carlo
> 
> 


Mime
View raw message