hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17951) Log the region's information in HRegion#checkResources
Date Tue, 25 Apr 2017 03:34:04 GMT

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

Anoop Sam John commented on HBASE-17951:

The chance of this breach may be rare. (?)  We have 128 MB default flush size and blocking
multiplier is 4.  So flush is too much lagged for the breach to happen.  But when it happens,
this patch will make too many warn logs. IMO also we should do some thing to limit the logs.
(Say once per breach or per some specified number of mutate calls)

> Log the region's information in HRegion#checkResources
> ------------------------------------------------------
>                 Key: HBASE-17951
>                 URL: https://issues.apache.org/jira/browse/HBASE-17951
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.3.0, 1.2.5
>            Reporter: Guangxu Cheng
>            Assignee: Guangxu Cheng
>         Attachments: HBASE-17951-master-v1.patch
> We throw RegionTooBusyException in HRegion#checkResources if above memstore limit. On
the server side,we just increment the value of blockedRequestsCount and do not print the
region's information.
> I think we should also print the region's information in server-side, so that we can
easily find the busy regions.

This message was sent by Atlassian JIRA

View raw message