You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Daryn Sharp (JIRA)" <ji...@apache.org> on 2013/03/22 22:45:17 UTC

[jira] [Created] (MAPREDUCE-5096) Deprecate ability to not cancel tokens when job completes

Daryn Sharp created MAPREDUCE-5096:
--------------------------------------

             Summary: Deprecate ability to not cancel tokens when job completes
                 Key: MAPREDUCE-5096
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5096
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
          Components: job submission
    Affects Versions: 2.0.0-alpha, 0.23.0, 3.0.0
            Reporter: Daryn Sharp
            Assignee: Daryn Sharp


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira