[ 
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
{\code}
export HBASE_OPTS="-XX:+UseG1GC -XX:MaxGCPauseMillis=200 
-XX:InitiatingHeapOccupancyPercent=60 -XX:G1HeapWastePercent=20 
-XX:G1MixedGCCountTarget=8"
{\code}

The last 2 parameters you mentioned seems critical.
Did you mean these two where changed?
{\code}
  <property>
    <name>hbase.hstore.flusher.count</name>
    <value>2</value>
    <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>
</property>
<property>
    <name>hbase.hstore.blockingStoreFiles</name>
    <value>10</value>
    <description> If more than this number of StoreFiles exist in any one Store 
(one StoreFile
     is written per flush of MemStore), updates are blocked for this region 
until a compaction is
      completed, or until hbase.hstore.blockingWaitTime has been 
exceeded.</description>
</property>
{\code}


> 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
(v6.3.4#6332)

Reply via email to