[
https://issues.apache.org/jira/browse/CASSANDRA-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366934#comment-14366934
]
Benedict commented on CASSANDRA-8851:
-------------------------------------
[~Hachmann]: it doesn't look like this log goes back far enough? Do you have an
earlier log? It also looks like your server is suffering severe GC pauses.
Would it be possible to get a heap dump uploaded somewhere, and also a result
of running "find ." in the root of your data directory, so we can rule out
potential causes ASAP (we're planning to get to the bottom of this before
releasing 2.1.4)?
> Uncaught exception on thread Thread[SharedPool-Worker-16,5,main] after
> upgrade to 2.1.3
> ---------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8851
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8851
> Project: Cassandra
> Issue Type: Bug
> Environment: ubuntu
> Reporter: Tobias Schlottke
> Assignee: Benedict
> Priority: Critical
> Fix For: 2.1.4
>
> Attachments: schema.txt, system.log.gz
>
>
> Hi there,
> after upgrading to 2.1.3 we've got the following error every few seconds:
> {code}
> WARN [SharedPool-Worker-16] 2015-02-23 10:20:36,392
> AbstractTracingAwareExecutorService.java:169 - Uncaught exception on thread
> Thread[SharedPool-Worker-16,5,main]: {}
> java.lang.AssertionError: null
> at org.apache.cassandra.io.util.Memory.size(Memory.java:307)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.utils.obs.OffHeapBitSet.capacity(OffHeapBitSet.java:61)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at org.apache.cassandra.utils.BloomFilter.indexes(BloomFilter.java:74)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.utils.BloomFilter.isPresent(BloomFilter.java:98)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.io.sstable.SSTableReader.getPosition(SSTableReader.java:1366)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.io.sstable.SSTableReader.getPosition(SSTableReader.java:1350)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.columniterator.SSTableSliceIterator.<init>(SSTableSliceIterator.java:41)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.filter.SliceQueryFilter.getSSTableColumnIterator(SliceQueryFilter.java:185)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.filter.QueryFilter.getSSTableColumnIterator(QueryFilter.java:62)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.CollationController.collectAllData(CollationController.java:273)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.CollationController.getTopLevelColumns(CollationController.java:62)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.ColumnFamilyStore.getTopLevelColumns(ColumnFamilyStore.java:1915)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1748)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:342)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:57)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:62)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> ~[na:1.7.0_45]
> at
> org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
> ~[apache-cassandra-2.1.3.jar:2.1.3]
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
> [apache-cassandra-2.1.3.jar:2.1.3]
> at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45]
> {code}
> This seems to crash the compactions and pushes up server load and piles up
> compactions.
> Any idea / possible workaround?
> Best,
> Tobias
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
