[
https://issues.apache.org/jira/browse/HDFS-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720248#comment-17720248
]
Viraj Jasani commented on HDFS-11063:
-------------------------------------
Thanks [~cnauroth], i was going through similar observation on thread dumps and
with some search, was able to find this old Jira, glad to see some discussion
is already present.
Do you think it is still worth pursuing this today? Maybe we can make this an
opt-in behavior just in case any user would be in favor of disabling it to
avoid redundant info in logs? At least this would be quite helpful for
debugging thread dumps.
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
