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/02/10 03:56:28 UTC
[jira] Moved: (HADOOP-6554) DelegationTokenSecretManager lifecycle
is inconsistent
[ https://issues.apache.org/jira/browse/HADOOP-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon moved HDFS-967 to HADOOP-6554:
------------------------------------------
Affects Version/s: (was: 0.22.0)
0.22.0
Key: HADOOP-6554 (was: HDFS-967)
Project: Hadoop Common (was: Hadoop HDFS)
> 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: 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.