From hdfs-issues-return-249368-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Mon Jan 28 20:06:07 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B0FFF18067A for ; Mon, 28 Jan 2019 20:06:06 +0100 (CET) Received: (qmail 84458 invoked by uid 500); 28 Jan 2019 19:06:05 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 84446 invoked by uid 99); 28 Jan 2019 19:06:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2019 19:06:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 40BBEC561A for ; Mon, 28 Jan 2019 19:06:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 0GtPSELiCP_J for ; Mon, 28 Jan 2019 19:06:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 94D885F5A7 for ; Mon, 28 Jan 2019 19:06:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C9038E26AE for ; Mon, 28 Jan 2019 19:06:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 91527243AA for ; Mon, 28 Jan 2019 19:06:00 +0000 (UTC) Date: Mon, 28 Jan 2019 19:06:00 +0000 (UTC) From: "Pranay Singh (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-14084) Need for more stats in DFSClient MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-14084?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1675= 4261#comment-16754261 ]=20 Pranay Singh commented on HDFS-14084: ------------------------------------- That's right so shall I remove the other two patches=C2=A0=C2=A0and rename= =C2=A0[^HDFS-14084.016.patch]=C2=A0to=C2=A0=C2=A0[^HDFS-14084.016.patch] > Need for more stats in DFSClient > -------------------------------- > > Key: HDFS-14084 > URL: https://issues.apache.org/jira/browse/HDFS-14084 > Project: Hadoop HDFS > Issue Type: Improvement > Affects Versions: 3.0.0 > Reporter: Pranay Singh > Assignee: Pranay Singh > Priority: Minor > Fix For: 3.3.0 > > Attachments: HDFS-14084.001.patch, HDFS-14084.002.patch, HDFS-140= 84.003.patch, HDFS-14084.004.patch, HDFS-14084.005.patch, HDFS-14084.006.pa= tch, HDFS-14084.007.patch, HDFS-14084.008.patch, HDFS-14084.009.patch, HDFS= -14084.010.patch, HDFS-14084.011.patch, HDFS-14084.012.patch, HDFS-14084.01= 3.patch, HDFS-14084.014.patch, HDFS-14084.015.patch, HDFS-14084.016.patch > > > The usage of HDFS has changed from being used as a map-reduce filesystem,= now it's becoming more of like a general purpose filesystem. In most of th= e cases there are issues with the Namenode so we have metrics to know the w= orkload or stress on Namenode. > However, there is a need to have more statistics collected for different = operations/RPCs in DFSClient to know which RPC operations are taking longer= time or to know what is the frequency of the operation.These statistics ca= n be exposed to the users of DFS Client and they can periodically log or do= some sort of flow control if the response is slow. This will also help to = isolate HDFS issue in a mixed environment where on a node say we have Spark= , HBase and Impala running together. We can check the throughput of differe= nt operation across client and isolate the problem caused because of noisy = neighbor or network congestion or shared JVM. > We have dealt with several problems from the field for which there is no = conclusive evidence as to what caused the problem. If we had metrics or sta= ts in DFSClient we would be better equipped to solve such complex problems. > List of jiras for reference: > ------------------------- > HADOOP-15538 HADOOP-15530 ( client side deadlock) -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org