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
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
