[
https://issues.apache.org/jira/browse/HADOOP-13762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095684#comment-16095684
]
Yonger commented on HADOOP-13762:
---------------------------------
I agree a thread name with meaningful information is a great idea, but I also
think logging the information you mentioned(userid, timestamp, and path) is
better than to insert into thread name from a comprehensive perspective. You
just need to put information into log component and without additional
complexity and performance consideration. And with these meaningful information
in logs, we also start a trouble shooting for performance problem, also this
approach applied in big company with high throughput computer system.
> S3A: Set thread names with more specific information about the call.
> --------------------------------------------------------------------
>
> Key: HADOOP-13762
> URL: https://issues.apache.org/jira/browse/HADOOP-13762
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Chris Nauroth
>
> Running {{jstack}} on a hung process and reading the stack traces is a
> helpful way to determine exactly what code in the process is stuck. This
> would be even more helpful if we included more descriptive information about
> the specific file system method call.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
