Flush Assertion Error - CF size changed during serialization
------------------------------------------------------------
Key: CASSANDRA-3482
URL: https://issues.apache.org/jira/browse/CASSANDRA-3482
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.2
Environment: RHEL 6
java version "1.6.0_26"
6 node cluster
Reporter: Dan Hendry
I have seen the following assert in the logs - there are no other suspicious or
unexpected log messages.
INFO [FlushWriter:9] 2011-11-10 13:08:58,882 Memtable.java (line 237) Writing
Memtable-UserData@1388955390(25676955/430716097 serialized/live bytes, 478913
ops)
ERROR [FlushWriter:9] 2011-11-10 13:08:59,513 AbstractCassandraDaemon.java
(line 133) Fatal exception in thread Thread[FlushWriter:9,5,main]
java.lang.AssertionError: CF size changed during serialization: was 4 initially
but 3 written
at
org.apache.cassandra.db.ColumnFamilySerializer.serializeForSSTable(ColumnFamilySerializer.java:94)
at
org.apache.cassandra.db.ColumnFamilySerializer.serializeWithIndexes(ColumnFamilySerializer.java:112)
at
org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:177)
at
org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:264)
at org.apache.cassandra.db.Memtable.access$400(Memtable.java:47)
at org.apache.cassandra.db.Memtable$4.runMayThrow(Memtable.java:289)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
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)
Once the error occurs, further MemtablePostFlusher tasks are blocked:
nodetool tpstats:
Pool Name Active Pending Completed Blocked All
time blocked
MemtablePostFlusher 1 18 16 0
0
It *seems* that all further flushed for the particular CF (in this case
UserData) will also result in the same assertion error. Restarting the node
fixes the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
