[
https://issues.apache.org/jira/browse/HBASE-28123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18090475#comment-18090475
]
Hudson commented on HBASE-28123:
--------------------------------
Results for branch branch-2.6
[build #480 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/480/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/480/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/480/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/480/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/480/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/480/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> TableRequests metrics broken after altering table
> -------------------------------------------------
>
> Key: HBASE-28123
> URL: https://issues.apache.org/jira/browse/HBASE-28123
> Project: HBase
> Issue Type: Bug
> Reporter: Bryan Beaudreault
> Assignee: Xiao Liu
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.7
>
>
> Alerting a table reopens all regions. I noticed after altering one of my
> tables that afterwards the TableRequests metrics no longer update. They seem
> stuck at whatever they were prior. I'm thinking this has something to do with
> the refactor done in https://issues.apache.org/jira/browse/HBASE-27681, which
> attempts to deregister metrics when a table is removed from the server. I
> think when it gets re-registered the new metrics aren't linked to whatever
> the jmx adapter is looking at.
> [~tianhang] FYI
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
