[jira] [Resolved] (CASSANDRA-3163) SlabAllocator OOMs much faster than HeapAllocator

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis resolved CASSANDRA-3163.
---------------------------------------

    Resolution: Fixed
      Reviewer: brandon.williams
      Assignee: Jonathan Ellis

committed

> 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.0
>         Environment: 3 nodes, 1G heap, RF=2
>            Reporter: Brandon Williams
>            Assignee: Jonathan Ellis
>             Fix For: 1.0.0
>
>         Attachments: 3163-v2.txt, 3163-v3.txt, 3163-v4.txt, 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