Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 14 Sep 2012 08:35:07 +1100 (NCT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1211349329.77379.1347572107837.JavaMail.jiratomcat@arcas>
In-Reply-To: <1662815429.63663.1347374947441.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (CASSANDRA-4644) Compaction error with Cassandra
 1.1.4 and LCS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-4644:
--------------------------------------

    Attachment: 4644.txt

Attachment adds sendBackToL0 code to promote, to fix this transparently instead of requiring offline scrub.

Not really a huge win since you still need scrub (off-or-online) to catch out-of-order rows within an sstable, but may help with some of the confusion around this.
                
> Compaction error with Cassandra 1.1.4 and LCS 
> ----------------------------------------------
>
>                 Key: CASSANDRA-4644
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4644
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.4
>         Environment: Cassandra 1.1.4, Ubuntu Lucid (2.6.32-346), Amazon EC2 m1.xlarge
>            Reporter: Rudolf VanderLeeden
>         Attachments: 4644.txt
>
>
> In our 1.1.4 testcluster of 3 nodes with RF=3, KS=1, and CF=5, we are getting an asserting error when running 'nodetool compact highscores leaderboard'. This stops compactions on the 'leaderboard' CF summing up to 11835 pending compactions. This error is seen only one one node. 
> The SSTables have originally been created on a 1.1.2 cluster with STCS and then copied to the testcluster also with 1.1.2. Repair, cleanup, compact were OK with STCS. Next, we changed to LCS and did again repair, cleanup, compact with success. 
> Then we started to use this LCS-based testcluster intensively and created lots of data and also large keys with millions of columns. 
> The assertion error in system.log :
>  INFO [CompactionExecutor:8] 2012-09-11 14:20:45,043 CompactionController.java (line 172) Compacting large row highscores/leaderboard:4c422d64626331353166372d363464612d343235342d396130322d6535616365343337373532332d676c6f62616c2d30 (72589650 bytes) incrementally
> ERROR [CompactionExecutor:8] 2012-09-11 14:20:50,336 AbstractCassandraDaemon.java (line 135) Exception in thread Thread[CompactionExecutor:8,1,RMI Runtime]
> java.lang.AssertionError
>         at org.apache.cassandra.db.compaction.LeveledManifest.promote(LeveledManifest.java:214)
>         at org.apache.cassandra.db.compaction.LeveledCompactionStrategy.handleNotification(LeveledCompactionStrategy.java:158)
>         at org.apache.cassandra.db.DataTracker.notifySSTablesChanged(DataTracker.java:531)
>         at org.apache.cassandra.db.DataTracker.replaceCompactedSSTables(DataTracker.java:254)
>         at org.apache.cassandra.db.ColumnFamilyStore.replaceCompactedSSTables(ColumnFamilyStore.java:992)
>         at org.apache.cassandra.db.compaction.CompactionTask.execute(CompactionTask.java:200)
>         at org.apache.cassandra.db.compaction.LeveledCompactionTask.execute(LeveledCompactionTask.java:50)
>         at org.apache.cassandra.db.compaction.CompactionManager$6.runMayThrow(CompactionManager.java:288)
>         at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         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)

--
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: http://www.atlassian.com/software/jira