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
This commit is contained in:
Wangda Tan 2018-04-27 13:07:38 -07:00
parent ef3ecc308d
commit b1833d9ba2

View File

@ -1111,7 +1111,6 @@ private void updateAMRMToken(Token token) throws IOException {
// 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()));
} }