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 10:11:20 GMT

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

Eshcar Hillel commented on HBASE-16417:

I used the same GC settings as you mentioned
export HBASE_OPTS="-XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:InitiatingHeapOccupancyPercent=60
-XX:G1HeapWastePercent=20 -XX:G1MixedGCCountTarget=8"

The last 2 parameters you mentioned seems critical.
Did you mean these two where changed?
    <description> The number of flush threads. With fewer threads, the MemStore flushes
will be
      queued. With more threads, the flushes will be executed in parallel, increasing the
load on
      HDFS, and potentially causing more compactions. </description>
    <description> If more than this number of StoreFiles exist in any one Store (one
     is written per flush of MemStore), updates are blocked for this region until a compaction
      completed, or until hbase.hstore.blockingWaitTime has been exceeded.</description>

> 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