cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10538) Assertion failed in LogFile when disk is full
Date Mon, 19 Oct 2015 16:04:05 GMT


Carl Yeksigian commented on CASSANDRA-10538:

Yeah, I destroyed the VM that generated the logs, but I'll run it again to see if I can reproduce
these errors.

> Assertion failed in LogFile when disk is full
> ---------------------------------------------
>                 Key: CASSANDRA-10538
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 3.x
>         Attachments: ma_txn_compaction_67311da0-72b4-11e5-9eb9-b14fa4bbe709.log, ma_txn_compaction_696059b0-72b4-11e5-9eb9-b14fa4bbe709.log,
ma_txn_compaction_8ac58b70-72b4-11e5-9eb9-b14fa4bbe709.log, ma_txn_compaction_8be24610-72b4-11e5-9eb9-b14fa4bbe709.log,
ma_txn_compaction_95500fc0-72b4-11e5-9eb9-b14fa4bbe709.log, ma_txn_compaction_a41caa90-72b4-11e5-9eb9-b14fa4bbe709.log
> [~carlyeks] was running a stress job which filled up the disk. At the end of the system
logs there are several assertion errors:
> {code}
> ERROR [CompactionExecutor:1] 2015-10-14 20:46:55,467 - Exception
in thread Thread[CompactionExecutor:1,1,main]
> java.lang.RuntimeException: Insufficient disk space to write 2097152 bytes
>         at org.apache.cassandra.db.compaction.writers.CompactionAwareWriter.getWriteDirectory(
>         at org.apache.cassandra.db.compaction.writers.MaxSSTableSizeWriter.realAppend(
>         at org.apache.cassandra.db.compaction.writers.CompactionAwareWriter.append(
>         at org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(
>         at ~[main/:na]
>         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.8.0_40]
>         at ~[na:1.8.0_40]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at [na:1.8.0_40]
> INFO  [IndexSummaryManager:1] 2015-10-14 21:10:40,099 -
Redistributing index summaries
> ERROR [IndexSummaryManager:1] 2015-10-14 21:10:42,275 - Exception
in thread Thread[IndexSummaryManager:1,1,main]
> java.lang.AssertionError: Already completed!
>         at org.apache.cassandra.db.lifecycle.LogFile.abort( ~[main/:na]
>         at org.apache.cassandra.db.lifecycle.LogTransaction.doAbort(
>         at org.apache.cassandra.utils.concurrent.Transactional$AbstractTransactional.abort(
>         at org.apache.cassandra.db.lifecycle.LifecycleTransaction.doAbort(
>         at org.apache.cassandra.utils.concurrent.Transactional$AbstractTransactional.abort(
>         at org.apache.cassandra.utils.concurrent.Transactional$AbstractTransactional.abort(
>         at org.apache.cassandra.utils.concurrent.Transactional$AbstractTransactional.close(
>         at
>         at$1.runMayThrow(
>         at ~[main/:na]
>         at org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolE
> {code}
> We should not have an assertion if it can happen when the disk is full, we should rather
have a runtime exception.
> I also would like to understand exactly what triggered the assertion. {{LifecycleTransaction}}
can throw at the beginning of the commit method if it cannot write the record to disk, in
which case all we have to do is ensure we update the records in memory after writing to disk
(currently we update them before). However, I am not sure this is what happened here, it looks
more like abort was called twice, which should never happen.

This message was sent by Atlassian JIRA

View raw message