hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-5096) Deprecate ability to not cancel tokens when job completes
Date Fri, 22 Mar 2013 21:45:17 GMT
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

View raw message