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 Wed, 26 Apr 2017 16:28:04 GMT

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

Anoop Sam John commented on HBASE-17951:

bq. private final LongAdder blockedRequestsCount = new LongAdder();
I believe some other jira did a perf optimization with changing this counter to LongAdder
from AtomicLong. Now we should not change back. :-(

> 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, HBASE-17951-master-v2.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