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 "Nikhil Mulley (JIRA)" <ji...@apache.org> on 2016/01/23 22:32:39 UTC

[jira] [Updated] (HDFS-9692) Report Top Namenode rpc consumers through JMX

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

Nikhil Mulley updated HDFS-9692:
--------------------------------
    Summary: Report Top Namenode rpc consumers through JMX  (was: Report top 10 Namenode rpc consumers through JMX)

> Report Top Namenode rpc consumers through JMX
> ---------------------------------------------
>
>                 Key: HDFS-9692
>                 URL: https://issues.apache.org/jira/browse/HDFS-9692
>             Project: Hadoop HDFS
>          Issue Type: Wish
>            Reporter: Nikhil Mulley
>
> Hi,
> I think it would really help if namenode(s) through metrics/jmx report the top rpc consumers, so it will be really handy to look at the rogue clients in times of despair/troubleshooting times.
> At times of rpc spikes on namenode, and callqueuelength increasing, it becomes tedious to figure out the offenders when there is a huge cluster (>1k nodes).
> Having rpc client information(src_host:src_port)  in the top consumers list would help operators. Let me know if any other information is needed to make this feature added to namenode metrics system.
> thank you
> Nikhil



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)