cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Issue Comment Edited: (CASSANDRA-208) OOM intermittently during compaction
Date Mon, 08 Jun 2009 22:14:07 GMT


Jonathan Ellis edited comment on CASSANDRA-208 at 6/8/09 3:12 PM:

208-2 fixes syncing of the bloom filter files.  this fixes the compactions failure and all
the others except timesort, which is not actually a new bug.

CASSANDRA-223 shows that the timesort failure is caused by a bug in TimeFilter that dates
back to the FB import.

      was (Author: jbellis):
    208-2 fixes syncing of the bloom filter files.  this fixes the compactions failure.
> OOM intermittently during compaction
> ------------------------------------
>                 Key: CASSANDRA-208
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         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.4
>         Attachments: 0001-CASSANDRA-208-cleanup.txt, 0002-r-m-touch.txt, 0003-split-sstable-into-data-index-and-bloom-filter-files.txt,
0004-fix-ColumnReader-add-tests.patch, 0005-fix-test-order-dependent-failures.patch, 208-2.patch,
> 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.

View raw message