[
https://issues.apache.org/jira/browse/MAPREDUCE-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546983#comment-13546983
]
Daryn Sharp commented on MAPREDUCE-4921:
----------------------------------------
There is that side affect. However the client has no cleanly defined way to
obtain the history other than via a token selector which isn't a generally
exposed api. Token management is a black art that I don't believe hadoop
components attempt to do.
Multiple renewer support might be useful. Or if there was more fine-grain
superuser proxy support so the HS or even NN could be configured to allow the
RM to only perform token renew/cancel operations.
Thanks for taking a look. I'll wrap up this patch.
> 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
