[
https://issues.apache.org/jira/browse/MAPREDUCE-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546672#comment-13546672
]
Siddharth Seth commented on MAPREDUCE-4921:
-------------------------------------------
Given, the history tokens are retrieved implicitly, and always given to the RM
to be managed - making this change seems ok.
A side affect of the history tokens, in general, seems to be that apps which
may have been trying to manage their own tokens, can't do so anymore. With this
patch, any attempt to renew / cancel would break. An alternate may be to allow
token renwal by the RM along with the specified renewer. Wouldn't help too much
though, since RM management would interfere with the client managing the tokens.
> JobClient should acquire HS token with RM principal
> ---------------------------------------------------
>
> Key: MAPREDUCE-4921
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4921
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: MAPREDUCE-4921.branch-23.patch
>
>
> The job client may acquire a history server token during job submission. The
> renewer is specified in a config value that the user must supply (for new
> api, a bit different for old api). If this value is not the RM's principal,
> then the RM cannot renew the token and long running jobs will fail. Since
> the token is implicitly acquired for the job, the HS token's renewer should
> always be the RM's principal.
--
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
