cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Wee <peich...@gmail.com>
Subject Re: ERROR Compaction Interrupted
Date Tue, 02 Jun 2015 06:54:26 GMT
looks like it is graciously handle in the code, should be okay.

                if (ci.isStopRequested())
                    throw new
CompactionInterruptedException(ci.getCompactionInfo());

https://github.com/apache/cassandra/blob/cassandra-2.0.9/src/java/org/apache/cassandra/db/compaction/CompactionTask.java#L156-L157

jason

On Tue, Jun 2, 2015 at 2:31 AM, Aiman Parvaiz <aiman@flipagram.com> wrote:

> Hi everyone,
> I am running C* 2.0.9 without vnodes and RF=2. Recently while repairing,
> rebalancing the cluster I encountered one instance of this(just one on one
> node):
>
> ERROR CompactionExecutor: <https://logentries.com/app/9f95dbd4#>55472
> CassandraDaemon.uncaughtException - Exception in thread Thread[
> CompactionExecutor: <https://logentries.com/app/9f95dbd4#>55472,1,main]
>
> May 30 19:31:09 cass-prod4.localdomain cassandra: 2015-05-30 19:31:09,991
> ERROR CompactionExecutor:55472 CassandraDaemon.uncaughtException -
> Exception in thread Thread[CompactionExecutor:55472,1,main]
>
> May 30 19:31:09 cass-prod4.localdomain
> org.apache.cassandra.db.compaction.CompactionInterruptedException:
> Compaction interrupted: Compaction@1b0b43e5-bef5-34f9-af08-405a7b58c71f(flipagram,
> home_feed_entry_index, 218409618/450008574)bytes
>
> May 30 19:31:09 cass-prod4.localdomain     at
> org.apache.cassandra.db.compaction.CompactionTask.runWith(CompactionTask.java:157)
> May 30 19:31:09 cass-prod4.localdomain     at
> org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48)
> May 30 19:31:09 cass-prod4.localdomain     at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> May 30 19:31:09 cass-prod4.localdomain     at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:60)
> May 30 19:31:09 cass-prod4.localdomain     at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:59)
> May 30 19:31:09 cass-prod4.localdomain     at
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run(CompactionManager.java:198)
> May 30 19:31:09 cass-prod4.localdomain     at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> May 30 19:31:09 cass-prod4.localdomain     at
> java.util.concurrent.FutureTask.run(FutureTask.java:262)
> May 30 19:31:09 cass-prod4.localdomain     at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> May 30 19:31:09 cass-prod4.localdomain     at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> May 30 19:31:09 cass-prod4.localdomain     at
> java.lang.Thread.run(Thread.java:745)
>
> After looking up a bit on the mailing list archives etc I understand that
> this might mean data corruption and I plan to take the node offline and
> replace it with a new one but still wanted to see if anyone can throw some
> light here about me missing out on something.
> Also, if this is a case of corrupted SST should I be concerned about it
> getting replicated and take care of it on the replication too.
>
> Thanks
>

Mime
View raw message