[ https://issues.apache.org/jira/browse/YARN-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611344#comment-13611344 ]
Hadoop QA commented on YARN-503: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12575120/YARN-503.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 tests included appear to have a timeout.{color} {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:red}-1 findbugs{color}. The patch appears to introduce 4 new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/581//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/581//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html Console output: https://builds.apache.org/job/PreCommit-YARN-Build/581//console This message is automatically generated. > DelegationTokens will be renewed forever if multiple jobs share tokens and > the first one sets JOB_CANCEL_DELEGATION_TOKEN to false > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-503 > URL: https://issues.apache.org/jira/browse/YARN-503 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 0.23.3, 3.0.0, 2.0.0-alpha > Reporter: Siddharth Seth > Assignee: Daryn Sharp > Attachments: YARN-503.patch > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira