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 "Arun Suresh (JIRA)" <ji...@apache.org> on 2017/09/29 20:53:05 UTC
[jira] [Updated] (HDFS-11063) Set NameNode RPC server handler
thread name with more descriptive information about the RPC call.
[ https://issues.apache.org/jira/browse/HDFS-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun Suresh updated HDFS-11063:
-------------------------------
Target Version/s: 3.1.0 (was: 2.9.0)
> Set NameNode RPC server handler thread name with more descriptive information about the RPC call.
> -------------------------------------------------------------------------------------------------
>
> Key: HDFS-11063
> URL: https://issues.apache.org/jira/browse/HDFS-11063
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Chris Nauroth
>
> We often run {{jstack}} on a NameNode process as a troubleshooting step if it is suffering high load or appears to be hanging. By reading the stack trace, we can identify if a caller is blocked inside an expensive operation. This would be even more helpful if we updated the RPC server handler thread name with more descriptive information about the RPC call. This could include the calling user, the called RPC method, and the most significant argument to that method (most likely the path).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org