hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brahma Reddy Battula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8929) Add a metric to expose the timestamp of the last journal
Date Wed, 26 Aug 2015 10:39:45 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712919#comment-14712919

Brahma Reddy Battula commented on HDFS-8929:

[~surendrasingh] thanks for wokring on this issue..

Patch overall looks good.. some minor nits

can you correct the following typos

1) `LastJournalTimestamp` | The timestamp of last  *successfuly written transections* 

2) @Metric("The timestamp of last  *successfuly written transections"* )

> 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
> 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

View raw message