You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Surendra Singh Lilhore (JIRA)" <ji...@apache.org> on 2015/09/02 18:46:46 UTC
[jira] [Updated] (HDFS-8929) Add a metric to expose the timestamp
of the last journal
[ https://issues.apache.org/jira/browse/HDFS-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Surendra Singh Lilhore updated HDFS-8929:
-----------------------------------------
Attachment: HDFS-8929-003.patch
Thanks [~brahmareddy] for review.
Attached updated patch, Please 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: New Feature
> Components: journal-node
> Reporter: Akira AJISAKA
> Assignee: Surendra Singh Lilhore
> Attachments: HDFS-8929-001.patch, HDFS-8929-002.patch, HDFS-8929-003.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)