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] [Updated] (CASSANDRA-3163) SlabAllocator OOMs much faster than HeapAllocator
Date Fri, 09 Sep 2011 13:28:08 GMT

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

Jonathan Ellis updated CASSANDRA-3163:
--------------------------------------

    Attachment: 3163.txt

What is happening is, the slab-allocated row keys are being put into the IndexSummary of the
new sstable on flush.  So the regions can only be GC's post-compaction.

> SlabAllocator OOMs much faster than HeapAllocator
> -------------------------------------------------
>
>                 Key: CASSANDRA-3163
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3163
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0
>         Environment: 3 nodes, 1G heap, RF=2
>            Reporter: Brandon Williams
>             Fix For: 1.0
>
>         Attachments: 3163.txt, system.log.gz
>
>
> SlabAllocator will OOM with stress at around 5.5M rows, which in this configuration is
roughly 3.3M rows per node.  Reverting to the HeapAllocator allowed all 10M rows to finish.
 Examining the SA heap dump in MAT just shows ~98% of the heap is in 'remainder'

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message