hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15102) HeapMemoryTuner can "overtune" memstore size and suddenly drop it into blocking zone
Date Wed, 20 Jan 2016 03:45:39 GMT

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

Hudson commented on HBASE-15102:

FAILURE: Integrated in HBase-Trunk_matrix #643 (See [https://builds.apache.org/job/HBase-Trunk_matrix/643/])
HBASE-15102 Fix HeapMemoryTuner overtuning memstore (eclark: rev 318814de28321a8a3d34cceea951bf164e3fa5af)
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultHeapMemoryTuner.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHeapMemoryManager.java

> HeapMemoryTuner can "overtune" memstore size and suddenly drop it into blocking zone
> ------------------------------------------------------------------------------------
>                 Key: HBASE-15102
>                 URL: https://issues.apache.org/jira/browse/HBASE-15102
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: Ashu Pachauri
>            Assignee: Ashu Pachauri
>            Priority: Critical
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>         Attachments: HBASE-15102-V0.patch, HBASE-15102-V1.patch, HBASE-15102-V2.patch,
> DefaultHeapMemoryTuner often resets the maximum step size for tuning to 8% of total heap
size. Often, when the size of memstore is to be decreased while tuning, the 8% tuning can
suddenly drop the memstore size below the low water mark of the previous memstore size (which
could potentially be  the used size of the memstore)
> This is problematic because suddenly it blocks all the updates by suddenly causing a
situation where memstore used size is above high water mark. This has a very bad performance
impact on an otherwise fine HBase cluster. 

This message was sent by Atlassian JIRA

View raw message