cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy
Date Tue, 05 Feb 2013 14:31:14 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis reopened CASSANDRA-5222:
---------------------------------------

      Assignee: Yuki Morishita

Aha... repair has to examine each sstable, it can't limit itself to 32 in L0.  So having L0
fall behind will screw you over like this.

Only quick fix I can think of is to fail repair until L0 gets under control -- say, 2x MAX_COMPACTING_L0.
                
> 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.1.6
>         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
>            Priority: Critical
>         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: http://www.atlassian.com/software/jira

Mime
View raw message