hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eshcar Hillel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
Date Wed, 21 Sep 2016 09:06:22 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509291#comment-15509291

Eshcar Hillel commented on HBASE-16417:

We've started working on the policy patch. 
We try to set a baseline for performance by running PE over the default memstore with the
configuration settings [~ram_krish] suggested in HBASE-14921.
*However* we are only able to complete the run with 2-4 threads, 10 regions (pre split)  writing
Any attempt to either increase the number of threads or the amount of data results in an Out
of Memory Error caused by the *GC*.
(I'm running with the same settings for PE, hbase and GC as you posted.)

We are running on a SSD 2.9PB disk (HDD wasn't even able to complete a run even with a single
thread), with 48GB RAM.

Some questions [~ram_krish]:
1. Did you run PE on an SSD or HDD?
2. How much memory do you have in your machine?
3. Can you think of any parameter that you forgot to mention that may have caused the difference
in executions? 

I'll also try running PE with more space for the GC and will update on the result.

> In-Memory MemStore Policy for Flattening and Compactions
> --------------------------------------------------------
>                 Key: HBASE-16417
>                 URL: https://issues.apache.org/jira/browse/HBASE-16417
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anastasia Braginsky
>            Assignee: Anastasia Braginsky
>             Fix For: 2.0.0

This message was sent by Atlassian JIRA

View raw message