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 "Haibin Huang (Jira)" <ji...@apache.org> on 2019/10/11 08:58:00 UTC

[jira] [Updated] (HDFS-14780) add ReportingNode to make the information of SlowPeersReport in namenode's jmx more specific

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

Haibin Huang updated HDFS-14780:
--------------------------------
    Summary: add ReportingNode to make the information of SlowPeersReport in namenode's jmx more specific  (was: make the information of SlowPeersReport in namenode's jmx more specific)

> add ReportingNode to make the information of SlowPeersReport in namenode's jmx more specific
> --------------------------------------------------------------------------------------------
>
>                 Key: HDFS-14780
>                 URL: https://issues.apache.org/jira/browse/HDFS-14780
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>            Reporter: Haibin Huang
>            Assignee: Haibin Huang
>            Priority: Major
>         Attachments: HDFS-14780
>
>
> I found *SlowPeersReport* in namenode's jmx is too simple, so i make an  inner class called org.apache.hadoop.hdfs.server.blockmanagement.SlowPeerTracker.*ReportingNode* to make SlowPeersReport's information more specific.Here is an example, the old SlowPeersReport maybe like this:
>  
> {code:java}
> "SlowPeersReport" :[{"SlowNode":"node4","ReportingNodes":["node1"]},{"SlowNode":"node2","ReportingNodes":["node1","node3"]},{"SlowNode":"node1","ReportingNodes":["node2"]}]{code}
>  
> we can see that the old SlowPeersReport just can tell you who is reporting the slownode, actually we can get more information by using the  inner class *ReportingNode* :
>  
> {code:java}
> "SlowPeersReport" :[{"SlowNode":"node4","ReportingNodes":[{"nodeId":"node1","averageDelay":2000.0,"reportTime":"Tue Aug 27 16:44:49 CST 2019"}]},{"SlowNode":"node2","ReportingNodes":[{"nodeId":"node1","averageDelay":2000.0,"reportTime":"Tue Aug 27 16:44:49 CST 2019"},{"nodeId":"node3","averageDelay":1000.0,"reportTime":"Tue Aug 27 16:44:49 CST 2019"}]},{"SlowNode":"node1","ReportingNodes":[{"nodeId":"node2","averageDelay":2000.0,"reportTime":"Tue Aug 27 16:44:49 CST 2019"}]}]{code}
>  
> we can know the *averageDelay* of reportingnode sending packet to slownode, and the *reportTime* can tell us when this message reporting to namenode.I think these message will be helpful for us to analyze the slownode problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org