[MAPREDUCE-5096] Deprecate ability to not cancel tokens when job completes

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.23.0, 2.0.0-alpha, 3.0.0-alpha1
• Component/s: job submission
• Target Version/s: 2.1.0-beta
• Assignee: Daryn Sharp
• Reporter: Daryn Sharp
• Created: 22/Mar/13 21:44
• Updated: 12/May/16 18:23

Description

MR provides a config mapreduce.job.complete.cancel.delegation.tokens and an api Job#setCancelDelegationTokenUponJobCompletion to disable canceling tokens when a job completes. This functionality appears to only be a workaround for the RM's inability to track tokens are being used by multiple apps. Hence, w/o this setting, oozie & pig jobs will fail after the first sub-job completes and the tokens are cancelled.

YARN-503 properly tracks tokens used by multiple jobs, which likely negates the need to specify not canceling tokens.

Issue Links

• requires: YARN-503 DelegationTokens will be renewed forever if multiple jobs share tokens and the first one sets JOB_CANCEL_DELEGATION_TOKEN to false