[ 
https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754140#comment-13754140
 ] 

Vinod Kumar Vavilapalli commented on YARN-1107:
-----------------------------------------------

Thinking back, I am increasingly getting uncomfortable with this solution, it 
all seems like a hack. How about this solution (which incidentally was the 
first solution that occurred to me):
 - Start the TokenRenewer only after ClientRMService starts.
 - During recovery, just enqueue all the token-requests
 - It is TokenRenewer's responsibility to set up the short-cut. ClientRMService 
shouldn't have any knowledge of this.
 - Globally, there is a dependency of starting TokenRenewer after 
ClientRMService.

This seems much natural to me. Shouldn't be too much of a change too. Thoughts?
                
> 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
>         Attachments: rm.log, YARN-1107.20130828.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

Reply via email to