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 "Kousuke Saruta (JIRA)" <ji...@apache.org> on 2013/11/19 02:59:21 UTC

[jira] [Created] (HADOOP-10113) There are some threads which will be dead silently when uncaught exception/error occured

Kousuke Saruta created HADOOP-10113:
---------------------------------------

             Summary: There are some threads which will be dead silently when uncaught exception/error occured
                 Key: HADOOP-10113
                 URL: https://issues.apache.org/jira/browse/HADOOP-10113
             Project: Hadoop Common
          Issue Type: Bug
    Affects Versions: 3.0.0
            Reporter: Kousuke Saruta
             Fix For: 3.0.0


Related to HDFS-5500, I found there are some threads be dead silently when uncaught exception/error occured.
For example, following threads are I mentioned.

* refreshUsed in DU
* reloader in ReloadingX509TrustManager
* t in UserGroupInformation#spawnAutoRenewalThreadForUserCreds
* errThread in Shell#runCommand
* sinkThread in MetricsSinkAdapter
* blockScannerThread in DataBlockScanner
* emptier in NameNode#startTrashEmptier (when we use TrashPolicyDefault) 

There are some critical threads if we can't notice the dead (e.g DU). I think we should handle those exception/error, and monitor the liveness or log that.



--
This message was sent by Atlassian JIRA
(v6.1#6144)