[
https://issues.apache.org/jira/browse/HADOOP-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832094#action_12832094
]
Tom White commented on HADOOP-6554:
-----------------------------------
Sort of related: I'm not sure of the wisdom of exiting the VM in
ExpiredTokenRemover when a Throwable is caught. Would it not be better for the
client of AbstractDelegationTokenSecretManager to determine what action to take
in this case?
> 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.
