[ https://issues.apache.org/jira/browse/CASSANDRA-8689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320482#comment-14320482 ]
Benedict commented on CASSANDRA-8689: ------------------------------------- It looks like that is something else entirely, caused by that test leaving an infinite loop of summary redistribution running. I've filed CASSANDRA-8805 to deal with that. So, those two patches together fixes the problem, although why that is I am not certain. > Assertion error in 2.1.2: ERROR [IndexSummaryManager:1] > ------------------------------------------------------- > > Key: CASSANDRA-8689 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8689 > Project: Cassandra > Issue Type: Bug > Reporter: Jeff Liu > Assignee: Benedict > Fix For: 2.1.3 > > Attachments: 8689-test.txt > > > After upgrading a 6 nodes cassandra from 2.1.0 to 2.1.2, start getting the > following assertion error. > {noformat} > ERROR [IndexSummaryManager:1] 2015-01-26 20:55:40,451 > CassandraDaemon.java:153 - Exception in thread > Thread[IndexSummaryManager:1,1,main] > java.lang.AssertionError: null > at org.apache.cassandra.io.util.Memory.size(Memory.java:307) > ~[apache-cassandra-2.1.2.jar:2.1.2] > at > org.apache.cassandra.io.sstable.IndexSummary.getOffHeapSize(IndexSummary.java:192) > ~[apache-cassandra-2.1.2.jar:2.1.2] > at > org.apache.cassandra.io.sstable.SSTableReader.getIndexSummaryOffHeapSize(SSTableReader.java:1070) > ~[apache-cassandra-2.1.2.jar:2.1.2] > at > org.apache.cassandra.io.sstable.IndexSummaryManager.redistributeSummaries(IndexSummaryManager.java:292) > ~[apache-cassandra-2.1.2.jar:2.1.2] > at > org.apache.cassandra.io.sstable.IndexSummaryManager.redistributeSummaries(IndexSummaryManager.java:238) > ~[apache-cassandra-2.1.2.jar:2.1.2] > at > org.apache.cassandra.io.sstable.IndexSummaryManager$1.runMayThrow(IndexSummaryManager.java:139) > ~[apache-cassandra-2.1.2.jar:2.1.2] > at > org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) > ~[apache-cassandra-2.1.2.jar:2.1.2] > at > org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor$UncomplainingRunnable.run(DebuggableScheduledThreadPoolExecutor.java:77) > ~[apache-cassandra-2.1.2.jar:2.1.2] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > [na:1.7.0_45] > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > [na:1.7.0_45] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > [na:1.7.0_45] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > [na:1.7.0_45] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > [na:1.7.0_45] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > [na:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45] > {noformat} > cassandra service is still running despite the issue. Node has total 8G > memory with 2G allocated to heap. We are basically running read queries to > retrieve data out of cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)