You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/09/07 09:29:00 UTC
[jira] [Updated] (HADOOP-13762) S3A: Set thread names with more
specific information about the call.
[ https://issues.apache.org/jira/browse/HADOOP-13762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-13762:
------------------------------------
Parent Issue: HADOOP-14831 (was: HADOOP-13204)
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org