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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/03/04 08:14:27 UTC

[jira] Commented: (HADOOP-6554) DelegationTokenSecretManager lifecycle is inconsistent

    [ https://issues.apache.org/jira/browse/HADOOP-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841098#action_12841098 ] 

Todd Lipcon commented on HADOOP-6554:
-------------------------------------

Can someone please commit this trivial fix?

> DelegationTokenSecretManager lifecycle is inconsistent
> ------------------------------------------------------
>
>                 Key: HADOOP-6554
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6554
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-6554.txt, hadoop-6554.txt, hdfs-967.txt
>
>
> FSNamesystem.dtSecretManager is initialized in FSNamesystem.initialize(), but not started until activate(). In FSN.stop() it calls dtSecretManager.stopThreads so long as it's non-null, but doesn't check that the threads have started (ie activate() may never have been called). This causes an NPE in stopThreads()
> To fix this, stopThreads should check tokenRemoverThread against null before interrupting it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.