hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4921) JobClient should acquire HS token with RM principal
Date Wed, 09 Jan 2013 20:52:15 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Daryn Sharp updated MAPREDUCE-4921:

    Attachment: MAPREDUCE-4921.branch-23.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, 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

View raw message