Enrique Guinto created CASSANDRA-14147:
------------------------------------------
Summary: AssertionError on MemtablePostFlush
Key: CASSANDRA-14147
URL: https://issues.apache.org/jira/browse/CASSANDRA-14147
Project: Cassandra
Issue Type: Bug
Components: Local Write-Read Paths
Environment: * Apache Cassandra 3.11.0
* Windows Server 2016
* JVM vendor/version: Java HotSpot(TM) 64-Bit Server VM/1.8.0_40
Reporter: Enrique Guinto
I am seeing a lot of exceptions in my cluster
{{ERROR [MemtablePostFlush:194] 2018-01-05 00:19:50,354
CassandraDaemon.java:228 - Exception in thread
Thread[MemtablePostFlush:194,5,main]
java.lang.AssertionError: null
at
org.apache.cassandra.cache.ChunkCache$CachingRebufferer.<init>(ChunkCache.java:222)
~[apache-cassandra-3.11.0.jar:3.11.0]
at org.apache.cassandra.cache.ChunkCache.wrap(ChunkCache.java:175)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.io.util.FileHandle$Builder.maybeCached(FileHandle.java:412)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.io.util.FileHandle$Builder.complete(FileHandle.java:381)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.io.util.FileHandle$Builder.complete(FileHandle.java:331)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.io.sstable.format.big.BigTableWriter.openFinal(BigTableWriter.java:333)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.io.sstable.format.big.BigTableWriter.access$600(BigTableWriter.java:53)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.io.sstable.format.big.BigTableWriter$TransactionalProxy.doPrepare(BigTableWriter.java:374)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.utils.concurrent.Transactional$AbstractTransactional.prepareToCommit(Transactional.java:173)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.io.sstable.format.SSTableWriter.prepareToCommit(SSTableWriter.java:281)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.prepareToCommit(SimpleSSTableMultiWriter.java:101)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.db.ColumnFamilyStore$Flush.flushMemtable(ColumnFamilyStore.java:1153)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1088)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
~[na:1.8.0_40]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_40]
at
org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.concurrent.NamedThreadFactory$$Lambda$4/406765571.run(Unknown
Source) [apache-cassandra-3.11.0.jar:3.11.0]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40]}}
This seems to have the side effect of commit log not being cleaned up. Is this
similar to issue CASSANDRA-13897 ?
Is there a work around for this?
Any help is appreciated. Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
