You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/06/03 23:40:07 UTC
[jira] Commented: (CASSANDRA-208) OOM intermittently during
compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716073#action_12716073 ]
Jonathan Ellis commented on CASSANDRA-208:
------------------------------------------
03
split sstable into data, index, and bloom filter files
02
r/m 'touch' code that populates a cache that is never used (and never updated on compaction either, so it's buggy too)
01
cleanup. mostly just moving code around so its position makes more sense to me
> OOM intermittently during compaction
> ------------------------------------
>
> Key: CASSANDRA-208
> URL: https://issues.apache.org/jira/browse/CASSANDRA-208
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: trunk
> Environment: arch: x86_64
> os: Linux version 2.6.18-92.1.22.el5
> java: nio2-ea-bin-b99-linux-x64-05_feb_2009
> Reporter: Jiansheng Huang
> Assignee: Jonathan Ellis
> Priority: Critical
> Fix For: 0.3
>
> Attachments: 0001-CASSANDRA-208-cleanup.txt, 0002-r-m-touch-code-that-populates-a-cache-that-is-never.txt, 0003-split-sstable-into-data-index-and-bloom-filter-files.txt
>
>
> jvm crashes intermittently during compaction. Our test data set is not that big, less than 10 GB.
> When jvm is about to crash, we see that it consumes a lot of memory (exceeding the max heap size).
> The excessive memory usage during compaction is caused by the maintenance of blockIndexes_ in SSTable. this blockIndexes_ was only introduced to the apache version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.