[
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577196#comment-13577196
]
Jonathan Ellis commented on CASSANDRA-5222:
-------------------------------------------
Patch attached to implement the 2 * MAX_COMPACTING_L0 approach. Not 100% sure
that doValidationCompaction/CompactionInterruptedException is the right way to
handle the abort. Yuki?
I noticed that Validator.add already asserts that the row is in the range being
validated, so we must be doing a range check somewhere. Not sure where though.
In any case, that won't help with the OOM problem since we expect to be able
to eliminate negligible numbers of L0 sstables that way, which is the problem
here.
> OOM Exception during repair session with LeveledCompactionStrategy
> ------------------------------------------------------------------
>
> Key: CASSANDRA-5222
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.0
> Environment: 3Gb Heap(12Gb per node RAM)
> 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size
> =100Mb
> Reporter: Ivan Sobolev
> Assignee: Yuki Morishita
> Fix For: 1.1.11
>
> Attachments: 5222.txt, chunks.json, sstablescanner.png
>
>
> 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
