[jira] [Commented] (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:comment-tabpanel=17798212#comment-17798212
]
Balazs Meszaros commented on HBASE-20549:
-
[~zhangduo] No updates. I am fine if we drop this.
> 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: Michael Stack
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 3.0.0-beta-1
>
> 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}
>
>
>
> hbase.regionserver.global.memstore.size.min.range
>
> 0.39
>
>
>
> hbase.regionserver.global.memstore.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.min.range
>
> 0.39
>
>
> {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
(v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=17797391#comment-17797391
]
Duo Zhang commented on HBASE-20549:
---
Any updates here? [~meszibalu] [~reidchan]
Thanks.
> 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: Michael Stack
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 3.0.0-beta-1
>
> 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}
>
>
>
> hbase.regionserver.global.memstore.size.min.range
>
> 0.39
>
>
>
> hbase.regionserver.global.memstore.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.min.range
>
> 0.39
>
>
> {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
(v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=16553469#comment-16553469
]
stack commented on HBASE-20549:
---
What [~reidchan] says and should we move " ...blockCacheSize and memStoreSize
metrics ..." or add them to other beans?
> 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}
>
>
>
> hbase.regionserver.global.memstore.size.min.range
>
> 0.39
>
>
>
> hbase.regionserver.global.memstore.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.min.range
>
> 0.39
>
>
> {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)
[jira] [Commented] (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:comment-tabpanel=16532212#comment-16532212
]
Reid Chan commented on HBASE-20549:
---
"DEAD"(too many zero) may be caused by interval between chore(1min by default)
is too short to has anyting for tuner to tune?
> 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}
>
>
>
> hbase.regionserver.global.memstore.size.min.range
>
> 0.39
>
>
>
> hbase.regionserver.global.memstore.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.min.range
>
> 0.39
>
>
> {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)
[jira] [Commented] (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:comment-tabpanel=16532204#comment-16532204
]
Reid Chan commented on HBASE-20549:
---
What about adding few more counters for {{blockedFlush}}, {{unblockedFlush}},
{{inc/decMemStore}}, {{inc/decBlockCacheSize}}.
> 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}
>
>
>
> hbase.regionserver.global.memstore.size.min.range
>
> 0.39
>
>
>
> hbase.regionserver.global.memstore.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.min.range
>
> 0.39
>
>
> {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)
[jira] [Commented] (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:comment-tabpanel=16531603#comment-16531603
]
Hadoop QA commented on HBASE-20549:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
14s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
1s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
33s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
33s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
10m 7s{color} | {color:green} Patch does not cause any errors with Hadoop
2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}118m 34s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}159m 36s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestHStore |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-20549 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12930121/HBASE-20549.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 0b38ad63a6f4 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9
14:43:09 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 2d2d9957a7 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_171 |
| findbugs | v3.1.0-RC3 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/13488/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/13488/testReport/ |
|
[jira] [Commented] (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:comment-tabpanel=16531336#comment-16531336
]
Balazs Meszaros commented on HBASE-20549:
-
The mentioned BlockedFlushes, UnblockedFlushes, IncreaseBlockSize, ... are
strictly related to the tuner. There isn't any other code which updates those
metrics. The only exception is blockCacheSize and memStoreSize metrics, because
these metrics are independent from the tuner.
> 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}
>
>
>
> hbase.regionserver.global.memstore.size.min.range
>
> 0.39
>
>
>
> hbase.regionserver.global.memstore.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.max.range
>
> 0.41
>
>
>
> hfile.block.cache.size.min.range
>
> 0.39
>
>
> {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)
