Forcing a major compaction on an CF with indexed sub columns occasionally causes an error -----------------------------------------------------------------------------------------
Key: CASSANDRA-1306 URL: https://issues.apache.org/jira/browse/CASSANDRA-1306 Project: Cassandra Issue Type: Bug Affects Versions: 0.7 Reporter: Nate McCall Note that is is a function of ColumnFamilyStore's forceMajorCompaction ERROR 14:33:31,430 Uncaught exception in thread Thread[CompactionExecutor:1,5,main] java.util.concurrent.ExecutionException: java.io.IOException: Keys must be written in ascending order. at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.afterExecute(DebuggableThreadPoolExecutor.java:87) at org.apache.cassandra.db.CompactionManager$CompactionExecutor.afterExecute(CompactionManager.java:659) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:888) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.io.IOException: Keys must be written in ascending order. at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:69) at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:86) at org.apache.cassandra.db.CompactionManager.doCompaction(CompactionManager.java:350) at org.apache.cassandra.db.CompactionManager$5.call(CompactionManager.java:227) 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) ... 2 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.