cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Morton (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-2747) memtable flush during index build causes AssertionError
Date Tue, 07 Jun 2011 19:44:00 GMT
memtable flush during index build causes AssertionError

                 Key: CASSANDRA-2747
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.8.0
            Reporter: Aaron Morton
            Assignee: Aaron Morton

Noticed when loading a lot of rows and then creating secondary indexes using update CF via
the CLI. 

ERROR 18:56:25,008 Fatal exception in thread Thread[FlushWriter:3,5,main]
        at org.apache.cassandra.db.ColumnFamilyStore.createFlushWriter(
        at org.apache.cassandra.db.Memtable.writeSortedContents(
        at org.apache.cassandra.db.Memtable.access$400(
        at org.apache.cassandra.db.Memtable$3.runMayThrow(
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
        at java.util.concurrent.ThreadPoolExecutor$
{code} calls cfs.maybeSwitchMemtable() with writeCommitLog false. So a
null ReplayPosition is eventually passed to Memtable.writeSortedContents(). checks Descriptor.hasReplayPosition() and it looks like any 0.8 stats file
should have a ReplayPosition. 

Looks like cfs.maybeSwitchMemtable() should use ReplayPosition.NONE rather than null. Patch
looks easy, will also try to write a test.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message