[
https://issues.apache.org/jira/browse/CASSANDRA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-208:
-------------------------------------
Attachment: 0005-fix-test-order-dependent-failures.patch
I did have NameSortTest and TimeSortTest failing because they were extending
CFST and hence running those tests as well, which caused problems since those
sets of tests are supposed to be run independently. Making NST and TST not
inherit from CFST (which was only done for convenience) fixes that. Here is
the patch.
I haven't seen compactions et al ever fail, no.
> OOM intermittently during compaction
> ------------------------------------
>
> Key: CASSANDRA-208
> URL: https://issues.apache.org/jira/browse/CASSANDRA-208
> 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
>
>
> 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.
