You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2012/11/28 19:08:58 UTC
[jira] [Commented] (YARN-248) Restore
RMDelegationTokenSecretManager state on restart
[ https://issues.apache.org/jira/browse/YARN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505726#comment-13505726 ]
Tom White commented on YARN-248:
--------------------------------
I can think of a couple of options: i) persist RMDelegationTokenSecretManager's state (secret keys, all current delegation tokens), or ii) recover the delegation tokens from the persisted credentials of the applications to be recovered (and the secret keys from a filesystem or ZK store).
> Restore RMDelegationTokenSecretManager state on restart
> -------------------------------------------------------
>
> Key: YARN-248
> URL: https://issues.apache.org/jira/browse/YARN-248
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Tom White
>
> On restart, the RM creates a new RMDelegationTokenSecretManager with fresh state. This will cause problems for Oozie jobs running on secure clusters since the delegation tokens stored in the job credentials (used by the Oozie launcher job to submit a job to the RM) will not be recognized by the RM, and recovery will fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira