cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Hendry (Created) (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-3482) Flush Assertion Error - CF size changed during serialization
Date Thu, 10 Nov 2011 21:05:53 GMT
Flush Assertion Error - CF size changed during serialization

                 Key: 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 (line 237) Writing Memtable-UserData@1388955390(25676955/430716097
serialized/live bytes, 478913 ops)
ERROR [FlushWriter:9] 2011-11-10 13:08:59,513 (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(
        at org.apache.cassandra.db.ColumnFamilySerializer.serializeWithIndexes(
        at org.apache.cassandra.db.Memtable.writeSortedContents(
        at org.apache.cassandra.db.Memtable.access$400(
        at org.apache.cassandra.db.Memtable$4.runMayThrow(
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
        at java.util.concurrent.ThreadPoolExecutor$

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:!default.jspa
For more information on JIRA, see:


View raw message