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.
|Status||Open [ 1 ]||Patch Available [ 10002 ]|
|Fix Version/s||1.0.0 [ 12318240 ]|
|Target Version/s||1.0.0 [ 12318240 ]||1.0.0, 0.22.1 [ 12318240, 12319242 ]|