[
https://issues.apache.org/jira/browse/HBASE-30447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18125736#comment-18125736
]
Hudson commented on HBASE-30447:
--------------------------------
Results for branch branch-3.0
[build #33 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3.0/33/]:
(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-3.0/33/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3.0/33/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk21 hadoop3 checks{color}
-- For more information [see jdk21
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3.0/33/JDK21_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> Table-level metrics can stop updating until the RegionServer restarts
> ---------------------------------------------------------------------
>
> Key: HBASE-30447
> URL: https://issues.apache.org/jira/browse/HBASE-30447
> Project: HBase
> Issue Type: Bug
> Components: metrics
> Affects Versions: 2.0.0, 3.0.0
> Reporter: David Manning
> Assignee: David Manning
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.1.0, 3.0.1, 2.6.8
>
>
> It is possible for table-level metrics from
> {{MetricsTableWrapperAggregateImpl.java}} to stop updating, and continually
> produce the last static value until RegionServer restart.
> The cause is not known but the most likely result is some
> {{NullPointerException}} in the {{run}} method.
> Because an exception is not caught in the {{run}} method, the
> {{ScheduledFutureTask}} will no longer be scheduled after the uncaught
> exception is thrown.
> There is no logging, so the cause of us seeing this behavior is not currently
> known. But with this issue fix, we could have logging to identify the source
> of the exception, which could lead to other bug fixes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
