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 1270017257 for ; Thu, 12 Mar 2015 05:50:44 +0000 (UTC) Received: (qmail 47135 invoked by uid 500); 12 Mar 2015 05:50:38 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 47068 invoked by uid 500); 12 Mar 2015 05:50:38 -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 47055 invoked by uid 99); 12 Mar 2015 05:50:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2015 05:50:38 +0000 Date: Thu, 12 Mar 2015 05:50:38 +0000 (UTC) From: "Ming Ma (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-7491) Add incremental blockreport latency to DN metrics 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-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358133#comment-14358133 ] Ming Ma commented on HDFS-7491: ------------------------------- Thanks Xiaoyu and Chris. > Add incremental blockreport latency to DN metrics > ------------------------------------------------- > > Key: HDFS-7491 > URL: https://issues.apache.org/jira/browse/HDFS-7491 > Project: Hadoop HDFS > Issue Type: Improvement > Components: datanode > Reporter: Ming Ma > Assignee: Ming Ma > Priority: Minor > Fix For: 2.7.0 > > Attachments: HDFS-7491-2.patch, HDFS-7491-3.patch, HDFS-7491-4.patch, HDFS-7491-branch-2.patch, HDFS-7491.patch > > > In a busy cluster, IBR processing could be delayed due to NN FSNamesystem lock and cause NN to throw NotReplicatedYetException to DFSClient and thus increase the overall application latency. > This will be taken care of when we address the NN FSNamesystem lock contention issue. > It is useful if we can provide IBR latency metrics from DN's point of view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)