You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Balazs Meszaros (JIRA)" <ji...@apache.org> on 2018/07/03 12:53:01 UTC

[jira] [Updated] (HBASE-20549) Dead MBean: Hadoop:service=HBase,sub=Memory,name=RegionServer

     [ https://issues.apache.org/jira/browse/HBASE-20549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Balazs Meszaros updated HBASE-20549:
------------------------------------
    Attachment: HBASE-20549.master.001.patch

> Dead MBean: Hadoop:service=HBase,sub=Memory,name=RegionServer
> -------------------------------------------------------------
>
>                 Key: HBASE-20549
>                 URL: https://issues.apache.org/jira/browse/HBASE-20549
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Balazs Meszaros
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-20549.master.001.patch, Screen Shot 2018-05-08 at 10.05.57 PM.png
>
>
> I'm studying flushing and blocking memstores. I came across the MBean Hadoop:service=HBase,sub=Memory,name=RegionServer It looks promising with metrics on blocked flush time, etc. See below. All metrics are zero. I tried to get it going. It is connected to the heap tuner facitlity that we might want to turn on. I managed to get the latter going w/ below configs.... (need to dump out more on what this thing is doing because it is tricky enabling it)
> {code:java}
> <configuration>
>   <property>
>     <name>
>   hbase.regionserver.global.memstore.size.min.range
> </name>
> <value>0.39</value>
> </property>
>   <property>
>     <name>
>   hbase.regionserver.global.memstore.size.max.range
> </name>
> <value>0.41</value>
> </property>
>   <property>
>     <name>
> hfile.block.cache.size.max.range
> </name>
> <value>0.41</value>
> </property>
>   <property>
>     <name>
>       hfile.block.cache.size.min.range
> </name>
> <value>0.39</value>
> </property>
> </configuration>
> {code}
> ... but still the metrics are not updated.
> We should make this bean work whether tuning is on or off or remove it.
> !Screen Shot 2018-05-08 at 10.05.57 PM.png|width=440,height=692!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)