YARN-8210. AMRMClient logging on every heartbeat to track updation of AM RM token causes too many log lines to be generated in AM logs. (Suma Shivaprasad via wangda)

Change-Id: I70edd6e301fd5e78d479e1882aedc9332a0827aa
(cherry picked from commit b1833d9ba2)
(cherry picked from commit f9add5fdd9)
This commit is contained in:
Wangda Tan 2018-04-27 13:07:38 -07:00 committed by Jonathan Hung
parent 7d8ee990cd
commit 9a895a90d9
1 changed files with 0 additions and 1 deletions

View File

@ -945,7 +945,6 @@ public class AMRMClientImpl<T extends ContainerRequest> extends AMRMClient<T> {
// to ensure we replace the previous token setup by the RM. // to ensure we replace the previous token setup by the RM.
// Afterwards we can update the service address for the RPC layer. // Afterwards we can update the service address for the RPC layer.
UserGroupInformation currentUGI = UserGroupInformation.getCurrentUser(); UserGroupInformation currentUGI = UserGroupInformation.getCurrentUser();
LOG.info("Updating with new AMRMToken");
currentUGI.addToken(amrmToken); currentUGI.addToken(amrmToken);
amrmToken.setService(ClientRMProxy.getAMRMTokenService(getConfig())); amrmToken.setService(ClientRMProxy.getAMRMTokenService(getConfig()));
} }