[
https://issues.apache.org/jira/browse/HDFS-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B updated HDFS-8929:
--------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Release Note: Exposed a metric 'LastJournalTimestamp' for JournalNode
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.
Thanks [~ajisakaa] for reporting.
Thanks [~surendrasingh] for the contribution and thanks [~brahmareddy] for
review.
> Add a metric to expose the timestamp of the last journal
> --------------------------------------------------------
>
> Key: HDFS-8929
> URL: https://issues.apache.org/jira/browse/HDFS-8929
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: journal-node
> Reporter: Akira AJISAKA
> Assignee: Surendra Singh Lilhore
> Fix For: 2.8.0
>
> Attachments: HDFS-8929-001.patch, HDFS-8929-002.patch,
> HDFS-8929-003.patch, HDFS-8929-004.patch, HDFS-8929-005.patch
>
>
> If there are three JNs and only one JN is failing to journal, we can detect
> it by monitoring the difference of the last written transaction id among JNs
> from NN WebUI or JN metrics. However, it's difficult to define the threshold
> to alert because the increase rate of the number of transaction depends on
> how busy the cluster is. Therefore I'd like to propose a metric to expose the
> timestamp of the last journal. That way we can easily alert if a JN is
> failing to journal for some fixed period.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
