[YARN-320] RM should always be able to renew its own tokens

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.3-alpha, 0.23.6, 3.0.0-alpha1
• Fix Version/s: 2.0.3-alpha, 0.23.6
• Component/s: resourcemanager
• Target Version/s: 2.0.3-alpha, 0.23.6
• Assignee: Daryn Sharp
• Reporter: Daryn Sharp
• Created: 07/Jan/13 20:13
• Updated: 12/May/16 18:30
• Resolved: 09/Jan/13 19:35

Description

YARN-280 introduced fast-fail for job submissions with bad tokens. Unfortunately, other stack components like oozie and customers are acquiring RM tokens with a hardcoded dummy renewer value. These jobs would fail after 24 hours because the RM token couldn't be renewed, but fast-fail is failing them immediately. The RM should always be able to renew its own tokens submitted with a job. The renewer field may continue to specify an external user who can renew.