cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8580) AssertionErrors after activating unchecked_tombstone_compaction with leveled compaction
Date Thu, 08 Jan 2015 13:07:34 GMT


Marcus Eriksson commented on CASSANDRA-8580:

Could you post more of the log leading up to the exception? Want to see a line like "... Compacting

> AssertionErrors after activating unchecked_tombstone_compaction with leveled compaction
> ---------------------------------------------------------------------------------------
>                 Key: CASSANDRA-8580
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Björn Hachmann
> During our upgrade of Cassandra from version 2.0.7 to 2.1.2 we experienced a serious
problem regarding the setting unchecked_tombstone_compaction in combination with leveled compaction
> In order to prevent tombstone-threshold-warnings we activated the setting for a specific
table after the upgrade. Some time after that we observed new errors in our log files:
> INFO  [CompactionExecutor:184] 2014-12-11 12:36:06,597 - Compacting
> data/cassandra/data/system/compactions_in_progress/system-compactions_in_progress-ka-1847-Data.db'),
> (path='/data/cassandra/data/system/compactions_in_progress/system-compactions_in_progress-ka-1846-Data.db')]
> ERROR [CompactionExecutor:183] 2014-12-11 12:36:06,613 - Exception
in thread Thread[CompactionExecutor:183,1,main]
> java.lang.AssertionError: /data/cassandra/data/metrigo_prod/new_user_data/metrigo_prod-new_user_data-tmplink-ka-705732-Data.db
>         at
>         at org.apache.cassandra.db.compaction.CompactionTask.runWith(
>         at
>         at ~[apache-cassandra-2.1.2.jar:2.1.2]
>         at org.apache.cassandra.db.compaction.CompactionTask.executeInternal(
>         at org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(
>         at org.apache.cassandra.db.compaction.CompactionManager$
>         at java.util.concurrent.Executors$ ~[na:1.7.0_45]
>         at ~[na:1.7.0_45]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at [na:1.7.0_45]
> Obviously that error aborted the compaction and after some time the number of pending
compactions became very high on every node. Of course, this in turn had a negative impact
on several other metrics.
> After reverting the setting we had to restart all nodes. After that compactions could
finish again and the pending compactions could be worked off.

This message was sent by Atlassian JIRA

View raw message