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

Hudson commented on HBASE-28123:
--------------------------------

Results for branch branch-3
        [build #88 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/branch-3/88/]:
 (/) *{color:green}+1 overall{color}*
----
details (if available):



(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop 
client{color}


(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop 
client{color}


> 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)

Reply via email to