cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy
Date Tue, 05 Feb 2013 16:19:13 GMT


Yuki Morishita commented on CASSANDRA-5222:

This is not only for L0. Currently we are opening SSTBS for all sstable and then filter out
those that are out of range. We can change that to only open the sstables for the range we
are repairing. This change only still leaves the chance to OOM, so we can prevent repair to
perform when the number of sstables for given range is too large.
> OOM Exception during repair session with LeveledCompactionStrategy
> ------------------------------------------------------------------
>                 Key: CASSANDRA-5222
>                 URL:
>             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.10
>         Attachments: 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:

View raw message