cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitrii Saprykin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9126) java.lang.RuntimeException: Last written key DecoratedKey >= current key DecoratedKey
Date Sat, 22 Aug 2015 23:58:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708230#comment-14708230
] 

Dmitrii Saprykin commented on CASSANDRA-9126:
---------------------------------------------

I restarted 2 nodes with INFO log level and there were no errors since restart.
So for me solution (at least temporary) was to make 'nodetool scrub' for affected keyspace
and restart node after scrub. I will leave INFO log.level and if issue reappears post full
logs here. Can it be LCS overlap issue like in Darla Baker case? Do you advise to update to
latest 2.0.x to fix? I am asking because I see nothing connected with LCS fixes in 2.0.16
and 2.0.17 changelogs.

> java.lang.RuntimeException: Last written key DecoratedKey >= current key DecoratedKey
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9126
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9126
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: srinivasu gottipati
>            Priority: Critical
>             Fix For: 2.0.x
>
>         Attachments: cassandra-system.log
>
>
> Cassandra V: 2.0.14,
> Getting the following exceptions while trying to compact (I see this issue was raised
in earlier versions and marked as closed. However it still appears in 2.0.14). In our case,
compaction is not getting succeeded and keep failing with this error.:
> {code}java.lang.RuntimeException: Last written key DecoratedKey(3462767860784856708,
354038323137333038305f3330325f31355f474d4543454f) >= current key DecoratedKey(3462334604624154281,
354036333036353334315f3336315f31355f474d4543454f) writing into {code}
> .......
> Stacktrace:{code}
> 	at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:143)
> 	at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:166)
> 	at org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:167)
> 	at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> 	at org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:60)
> 	at org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:59)
> 	at org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run(CompactionManager.java:198)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745){code}
> Any help is greatly appreciated



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message