You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2021/02/19 18:00:00 UTC
[jira] [Commented] (HBASE-25539) Add metric for age of oldest wal.
[ https://issues.apache.org/jira/browse/HBASE-25539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287268#comment-17287268 ]
Hudson commented on HBASE-25539:
--------------------------------
Results for branch branch-2
[build #180 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/180/]: (/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/180/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/180/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/180/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/180/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Add metric for age of oldest wal.
> ---------------------------------
>
> Key: HBASE-25539
> URL: https://issues.apache.org/jira/browse/HBASE-25539
> Project: HBase
> Issue Type: Improvement
> Components: metrics, regionserver
> Affects Versions: 3.0.0-alpha-1, 1.6.0, 2.5.0, 2.4.2
> Reporter: Rushabh Shah
> Assignee: Rushabh Shah
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.2
>
>
> In our production clusters, we have seen multiple cases where some of the wals are lingering in zk replication queues for months and we have no insight into it. Recently we fixed one case where wal was getting stuck if it is 0 size and from old sources. HBASE-25536. It would be helpful if we can have some metric which will tell us the age of oldest wal and we can add an alert for monitoring purpose.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)