cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Falcao (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-5720) AssertionError in CompactionExecutor
Date Wed, 03 Jul 2013 16:36:20 GMT
Eric Falcao created CASSANDRA-5720:

             Summary: AssertionError in CompactionExecutor
                 Key: CASSANDRA-5720
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.2.5
         Environment: 4 nodes
RF 2
            Reporter: Eric Falcao

Seeing this on all 4 of my nodes during a major compaction.

ERROR [CompactionExecutor:57927] 2013-07-03 13:41:27,591 (line 175) Exception
in thread Thread[CompactionExecutor:57927,1,RMI Runtime]
java.lang.AssertionError: originally calculated column size of 443395646 but now it is 443395712
        at org.apache.cassandra.db.compaction.LazilyCompactedRow.write(
        at org.apache.cassandra.db.compaction.CompactionTask.runWith(
        at org.apache.cassandra.db.compaction.CompactionTask.executeInternal(
        at org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(
        at org.apache.cassandra.db.compaction.CompactionManager$6.runMayThrow(
        at java.util.concurrent.Executors$
        at java.util.concurrent.FutureTask$Sync.innerRun(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

A little bit about this CF. It stores data with a TTL of up to 30 days. These rows are wide.
We run major compactions to remove expired data. This has been our setup for almost 2 years
and this issue only started cropping up after upgrading to 1.2.5 (from 1.1.5)

I've been running scrub in the meantime to remove expired data. Now, I'm ending up with lots
of similarly sized SSTables that C* is trying constantly to compact. These minor compactions
of the bigger SSTables are failing also.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message