Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7893A187D1 for ; Sat, 5 Sep 2015 02:22:46 +0000 (UTC) Received: (qmail 70730 invoked by uid 500); 5 Sep 2015 02:22:46 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 70677 invoked by uid 500); 5 Sep 2015 02:22:46 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 70662 invoked by uid 99); 5 Sep 2015 02:22:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Sep 2015 02:22:46 +0000 Date: Sat, 5 Sep 2015 02:22:46 +0000 (UTC) From: "Brahma Reddy Battula (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-8929) Add a metric to expose the timestamp of the last journal MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731723#comment-14731723 ] Brahma Reddy Battula commented on HDFS-8929: -------------------------------------------- [~surendrasingh] thanks for updating the patch..Latest Patch LGTM,[~ajisakaa] do you have some comments on this latest patch..? > 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)