Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 16 Dec 2013 20:41:08 +0000 (UTC)
From: "Jimmy Xiang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12673513.1381535058819.45439.1387226468079@arcas>
In-Reply-To: <JIRA.12673513.1381535058819@arcas>
References: <JIRA.12673513.1381535058819@arcas>
Subject: [jira] [Updated] (HDFS-5350) Name Node should report fsimage
 transfer time as a metric
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jimmy Xiang updated HDFS-5350:
------------------------------

    Attachment: trunk-5350_v3.patch

Attached patch v3, moved the test to TestCheckpoint. It is hard to predict how many times getimage/getedit/putimage are called. So I just verified the metrics are updated generally.

> Name Node should report fsimage transfer time as a metric
> ---------------------------------------------------------
>
>                 Key: HDFS-5350
>                 URL: https://issues.apache.org/jira/browse/HDFS-5350
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Rob Weltman
>            Assignee: Jimmy Xiang
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: trunk-5350.patch, trunk-5350_v3.patch
>
>
> If the (Secondary) Name Node reported fsimage transfer times (perhaps the last ten of them), monitoring tools could detect slowdowns that might jeopardize cluster stability.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)