[
https://issues.apache.org/jira/browse/HBASE-25539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289130#comment-17289130
]
Hudson commented on HBASE-25539:
--------------------------------
Results for branch branch-1
[build #88 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/88/]:
(x) *{color:red}-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-1/88//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/88//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/88//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> 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, 1.7.0, 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)
