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 "Siddharth Seth (Created) (JIRA)" <ji...@apache.org> on 2012/03/07 01:31:58 UTC

[jira] [Created] (MAPREDUCE-3979) DelegationTokens will be renewed forever if multiple jobs share tokens and the first one sets JOB_CANCEL_DELEGATION_TOKEN to false

DelegationTokens will be renewed forever if multiple jobs share tokens and the first one sets JOB_CANCEL_DELEGATION_TOKEN to false
----------------------------------------------------------------------------------------------------------------------------------

                 Key: MAPREDUCE-3979
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3979
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: mrv2, resourcemanager
    Affects Versions: 1.0.0, 0.23.0
            Reporter: Siddharth Seth


The first Job/App to register a token is the one which DelegationTokenRenewer associates with a a specific Token. An attempt to remove/cancel these shared tokens by subsequent jobs doesn't work - since the JobId will not match.
As a result, Even if subsequent jobs have MRJobConfig.JOB_CANCEL_DELEGATION_TOKEN set to true - tokens will not be cancelled when those jobs complete.
Tokens will eventually be removed from the RM / JT when the service that issued them considers them to have expired or via an explicit cancelDelegationTokens call (not implemented yet in 23).
A side affect of this is that the same delegation token will end up being renewed multiple times (a separate TimerTask for each job which uses the token).

DelegationTokenRenewer could maintain a reference count/list of jobIds for shared tokens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira