[
https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760757#comment-13760757
]
Omkar Vinit Joshi commented on YARN-1107:
-----------------------------------------
Thanks Vinod..
bq. Put both RMDelegationTokenSecretManager and ClientRMService in RMContext.
Then you don't need delegationTokenRenewer.setClientRMService() and
ClientRMService.getDelegationTokenSecretManager().
bq. You can add an assert in DelegationTokenRenewer.serviceStart() to check for
ClientRMService.start() after the comment. It'll be useful if tests enable
assertions, can you check?
done..
bq. RMDelegationTokenIdentifier.Renewer.setSecretManager is moved into
ClientRMService, but not so in the test. Can we change that.
fixed
bq. Please also take care of the test-issue and the findbugs warning.
Done..
> Job submitted with Delegation token in secured environment causes RM to fail
> during RM restart
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-1107
> URL: https://issues.apache.org/jira/browse/YARN-1107
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.1.0-beta
> Reporter: Arpit Gupta
> Assignee: Omkar Vinit Joshi
> Priority: Blocker
> Fix For: 2.1.1-beta
>
> Attachments: rm.log, YARN-1107.20130828.1.patch,
> YARN-1107.20130829.1.patch, YARN-1107.20130904.1.patch
>
>
> If secure RM with recovery enabled is restarted while oozie jobs are running
> rm fails to come up.
--
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
