ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMBARI-13109) Verify that max logs parameter wouldn't cause premature region flush
Date Fri, 22 Sep 2017 02:43:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120333#comment-16120333
] 

Ted Yu edited comment on AMBARI-13109 at 9/22/17 2:42 AM:
----------------------------------------------------------

The max logs parameter plays an important role in preventing fragmentation in memstore.


was (Author: yuzhihong@gmail.com):
The max logs parameter plays an important role in preventing fragmentation in memstore .

> Verify that max logs parameter wouldn't cause premature region flush
> --------------------------------------------------------------------
>
>                 Key: AMBARI-13109
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13109
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Ted Yu
>
> For hbase, the following relationship should be maintained:
> dfs.blocksize * 0.95 *  hbase.regionserver.maxlogs (default 32) > hbase.regionserver.global.memstore.upperLimit
* HBASE_HEAPSIZE
> The rationale is to avoid premature region flush due to log roll which is triggered by
insufficiently high max logs.
> When user changes the values for max logs, memstore upper limit or max heap size, we
should verify that the above relationship is satisfied.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message