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 "Daniel Templeton (JIRA)" <ji...@apache.org> on 2018/11/02 21:07:00 UTC
[jira] [Updated] (HDFS-14015) Improve error handling in
hdfsThreadDestructor in native thread local storage
[ https://issues.apache.org/jira/browse/HDFS-14015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Templeton updated HDFS-14015:
------------------------------------
Attachment: HDFS-14015.007.patch
> Improve error handling in hdfsThreadDestructor in native thread local storage
> -----------------------------------------------------------------------------
>
> Key: HDFS-14015
> URL: https://issues.apache.org/jira/browse/HDFS-14015
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: native
> Affects Versions: 3.0.0
> Reporter: Daniel Templeton
> Assignee: Daniel Templeton
> Priority: Major
> Attachments: HDFS-14015.001.patch, HDFS-14015.002.patch, HDFS-14015.003.patch, HDFS-14015.004.patch, HDFS-14015.005.patch, HDFS-14015.006.patch, HDFS-14015.007.patch
>
>
> In the hdfsThreadDestructor() function, we ignore the return value from the DetachCurrentThread() call. We are seeing cases where a native thread dies while holding a JVM monitor, and it doesn't release the monitor. We're hoping that logging this error instead of ignoring it will shed some light on the issue. In any case, it's good programming practice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org