You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/11/13 23:09:13 UTC
[jira] Commented: (CASSANDRA-1744) Compaction errors: "Keys must be
written in ascending order"
[ https://issues.apache.org/jira/browse/CASSANDRA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931737#action_12931737 ]
Jonathan Ellis commented on CASSANDRA-1744:
-------------------------------------------
Do you have r1034634 where I reverted a change to DK comparator?
> Compaction errors: "Keys must be written in ascending order"
> ------------------------------------------------------------
>
> Key: CASSANDRA-1744
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1744
> Project: Cassandra
> Issue Type: Bug
> Reporter: Brandon Williams
> Fix For: 0.7.0
>
>
> When compaction starts, many of these exceptions are thrown:
> ERROR 16:53:00,252 non-fatal error during compaction
> java.io.IOException: Keys must be written in ascending order.
> at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:134)
> at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:151)
> at org.apache.cassandra.db.CompactionManager.doCompaction(CompactionManager.java:279)
> at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:109)
> at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:87)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:636)
> Easily reproduced with stress.py
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.