[ https://issues.apache.org/jira/browse/YARN-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320275#comment-14320275 ]
Hudson commented on YARN-3104: ------------------------------ FAILURE: Integrated in Hadoop-Mapreduce-trunk #2054 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2054/]) YARN-3104. Fixed RM to not generate new AMRM tokens on every heartbeat between rolling and activation. Contributed by Jason Lowe (jianhe: rev 18297e09727e4af95140084760ae1267e8fe51c4) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/RMAppAttemptImpl.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/security/TestAMRMTokens.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockAM.java * hadoop-yarn-project/CHANGES.txt > RM generates new AMRM tokens every heartbeat between rolling and activation > --------------------------------------------------------------------------- > > Key: YARN-3104 > URL: https://issues.apache.org/jira/browse/YARN-3104 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.6.0 > Reporter: Jason Lowe > Assignee: Jason Lowe > Fix For: 2.7.0 > > Attachments: YARN-3104.001.patch, YARN-3104.002.patch, > YARN-3104.003.patch > > > When the RM rolls a new AMRM secret, it conveys this to the AMs when it > notices they are still connected with the old key. However neither the RM > nor the AM explicitly close the connection or otherwise try to reconnect with > the new secret. Therefore the RM keeps thinking the AM doesn't have the new > token on every heartbeat and keeps sending new tokens for the period between > the key roll and the key activation. Once activated the RM no longer squawks > in its logs about needing to generate a new token every heartbeat (i.e.: > second) for every app, but the apps can still be using the old token. The > token is only checked upon connection to the RM. The apps don't reconnect > when sent a new token, and the RM doesn't force them to reconnect by closing > the connection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)