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
)
This commit is contained in:
parent
b3fd464e55
commit
f9add5fdd9
|
@ -1111,7 +1111,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()));
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue