hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3475) JT can't renew its own tokens
Date Mon, 28 Nov 2011 18:41:40 GMT

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

Owen O'Malley commented on MAPREDUCE-3475:
------------------------------------------

Actually, I think this is the wrong direction. In general the JT should renew its own tokens.

I'd suggest rather that the broken tokens from Oozie not be renewed by not trying to renew
any tokens that don't have the proper user as either owner or renewer. That is a much more
general fix that will handle a wider set of upstream problems.
                
> JT can't renew its own tokens
> -----------------------------
>
>                 Key: MAPREDUCE-3475
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3475
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.20.205.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: MAPREDUCE-3475.patch
>
>
> When external systems submit jobs whose tasks need to submit additional jobs (such as
oozie/pig), they include their own MR token used to submit the job.  The token's renewer may
not allow the JT to renew the token.  The JT log will include very long SASL/GSSAPI exceptions
when the job is submitted.  It is also dubious for the JT to renew its token because it renders
the expiry as meaningless since the JT will renew its own token until the max lifetime is
exceeded.
> After speaking with Owen & Jitendra, the immediate solution is for the JT to not
attempt to renew its own tokens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message