You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/05/18 03:52:00 UTC
[jira] [Updated] (AMBARI-23353) Provide sanity check for hbase in
memory flush parameters
[ https://issues.apache.org/jira/browse/AMBARI-23353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated AMBARI-23353:
----------------------------
Description:
For hbase 2.0 release, there is correlation between the following parameters:
* hbase.memstore.inmemoryflush.threshold.factor : threshold for the active segment
* hbase.hregion.compacting.pipeline.segments.limit : pipeline length
For SSD, a threshold of 2% for the active segment (hbase.memstore.inmemoryflush.threshold.factor=0.02) and pipeline length of 4 (hbase.hregion.compacting.pipeline.segments.limit=4).
For HDD, hbase.hregion.compacting.pipeline.segments.limit should be 3 (due to lower throughput of HDD).
was:
For hbase 2.0 release, there is correlation between the following parameters:
* hbase.memstore.inmemoryflush.threshold.factor : threshold for the active segment
* hbase.hregion.compacting.pipeline.segments.limit : pipeline length
For SSD, a threshold of 2% for the active segment (hbase.memstore.inmemoryflush.threshold.factor=0.02) and pipeline length of 4 (hbase.hregion.compacting.pipeline.segments.limit=4).
For HDD, hbase.hregion.compacting.pipeline.segments.limit should be 3 (due to lower throughput of HDD).
> Provide sanity check for hbase in memory flush parameters
> ---------------------------------------------------------
>
> Key: AMBARI-23353
> URL: https://issues.apache.org/jira/browse/AMBARI-23353
> Project: Ambari
> Issue Type: Task
> Reporter: Ted Yu
> Priority: Major
>
> For hbase 2.0 release, there is correlation between the following parameters:
> * hbase.memstore.inmemoryflush.threshold.factor : threshold for the active segment
> * hbase.hregion.compacting.pipeline.segments.limit : pipeline length
> For SSD, a threshold of 2% for the active segment (hbase.memstore.inmemoryflush.threshold.factor=0.02) and pipeline length of 4 (hbase.hregion.compacting.pipeline.segments.limit=4).
> For HDD, hbase.hregion.compacting.pipeline.segments.limit should be 3 (due to lower throughput of HDD).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)