Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 11 Nov 2014 18:34:33 +0000 (UTC)
From: "Joshua McKenzie (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12750708.1414402812000.470809.1415730873819@Atlassian.JIRA>
In-Reply-To: <JIRA.12750708.1414402812000@Atlassian.JIRA>
References: <JIRA.12750708.1414402812000@Atlassian.JIRA>
 <JIRA.12750708.1414402812359@arcas>
Subject: [jira] [Commented] (CASSANDRA-8192) AssertionError in Memory.java
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206771#comment-14206771 ] 

Joshua McKenzie commented on CASSANDRA-8192:
--------------------------------------------

A trivial attempt to reproduce w/heap memory bounded to 512M on a 32-bit jvm on 32-bit Windows doesn't reproduce any of the above errors w/stress.  In a more "production" type environment, however, you're not going to have almost any breathing room to create CF's or really do anything due to fixed memory overhead per CF from the slab allocator combined with a very small heap.

You really need to be running with more than 512M allocated to cassandra - a 32-bit JVM, 32-bit OS, and 512m heap is far outside the bounds of recommended or required specs.  You should be able to go up to at least 1.4G ([reference|http://www.oracle.com/technetwork/java/hotspotfaq-138619.html#gc_heap_32bit]) which may help alleviate some of these problems, though it's still not something one would consider for heavy production use.

Re: CASSANDRA-6283: you'll still see those error messages due to a race in CompactionScanner closing vs. sstables being deleted but should not see permanent accumulation of files requiring node restart.  This is being addressed in CASSANDRA-8019.

Re: the other errors: I would be hesitant to take those errors at face-value as you've been OOM'ing on these nodes as per CASSANDRA-8070 and other tickets you've opened regarding 2.1.1.

> AssertionError in Memory.java
> -----------------------------
>
>                 Key: CASSANDRA-8192
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8192
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Windows-7-32 bit, 3GB RAM, Java 1.7.0_67
>            Reporter: Andreas Schnitzerling
>            Assignee: Joshua McKenzie
>         Attachments: cassandra.bat, cassandra.yaml, system.log
>
>
> Since update of 1 of 12 nodes from 2.1.0-rel to 2.1.1-rel Exception during start up.
> {panel:title=system.log}
> ERROR [SSTableBatchOpen:1] 2014-10-27 09:44:00,079 CassandraDaemon.java:153 - Exception in thread Thread[SSTableBatchOpen:1,5,main]
> java.lang.AssertionError: null
> 	at org.apache.cassandra.io.util.Memory.size(Memory.java:307) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.compress.CompressionMetadata.<init>(CompressionMetadata.java:135) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.compress.CompressionMetadata.create(CompressionMetadata.java:83) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.util.CompressedSegmentedFile$Builder.metadata(CompressedSegmentedFile.java:50) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.util.CompressedPoolingSegmentedFile$Builder.complete(CompressedPoolingSegmentedFile.java:48) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.sstable.SSTableReader.load(SSTableReader.java:766) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.sstable.SSTableReader.load(SSTableReader.java:725) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:402) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:302) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at org.apache.cassandra.io.sstable.SSTableReader$4.run(SSTableReader.java:438) ~[apache-cassandra-2.1.1.jar:2.1.1]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[na:1.7.0_55]
> 	at java.util.concurrent.FutureTask.run(Unknown Source) ~[na:1.7.0_55]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.7.0_55]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.7.0_55]
> 	at java.lang.Thread.run(Unknown Source) [na:1.7.0_55]
> {panel}
> In the attached log you can still see as well CASSANDRA-8069 and CASSANDRA-6283.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)