You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Íñigo Goiri (JIRA)" <ji...@apache.org> on 2018/11/30 02:23:00 UTC
[jira] [Comment Edited] (HDFS-14084) Need for more stats in
DFSClient
[ https://issues.apache.org/jira/browse/HDFS-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704154#comment-16704154 ]
Íñigo Goiri edited comment on HDFS-14084 at 11/30/18 2:22 AM:
--------------------------------------------------------------
{code}
Íñigo Goiri the issue is that we don't have enough metrics on DFSClient side, so it is hard to troubleshoot issues at the client side.
{code}
I got that; I'm just pointing out that we should use some of the code abstraction already existing in Hadoop like having proper classes and using metric counters. Right now, this is implemented raw while there are helper tools already available.
To be more specific, check the implementations of RPCServer.
They don't need to wrap every single function they want to monitor.
There is a framework that captures every call and tracks it.
This should use a similar approach where all calls are monitored without having to wrap one by one.
was (Author: elgoiri):
{code}
Íñigo Goiri the issue is that we don't have enough metrics on DFSClient side, so it is hard to troubleshoot issues at the client side.
{code}
I got that; I'm just pointing out that we should use some of the code abstraction already existing in Hadoop like having proper classes and using metric counters. Right now, this is implemented raw while there are helper tools already available.
> 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
> Attachments: HDFS-14084.001.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 the cases there are issues with the Namenode so we have metrics to know the workload 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 can 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 different 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 stats 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