YARN-3383. AdminService should use warn instead of info to log exception when operation fails. (Li Lu via wangda)
This commit is contained in:
parent
eda02540ce
commit
97a7277a2d
|
@ -103,6 +103,9 @@ Release 2.8.0 - UNRELEASED
|
|||
YARN-3241. FairScheduler handles "invalid" queue names inconsistently.
|
||||
(Zhihai Xu via kasha)
|
||||
|
||||
YARN-3383. AdminService should use "warn" instead of "info" to log exception
|
||||
when operation fails. (Li Lu via wangda)
|
||||
|
||||
Release 2.7.0 - UNRELEASED
|
||||
|
||||
INCOMPATIBLE CHANGES
|
||||
|
|
|
@ -699,7 +699,7 @@ public class AdminService extends CompositeService implements
|
|||
|
||||
private YarnException logAndWrapException(Exception exception, String user,
|
||||
String argName, String msg) throws YarnException {
|
||||
LOG.info("Exception " + msg, exception);
|
||||
LOG.warn("Exception " + msg, exception);
|
||||
RMAuditLogger.logFailure(user, argName, "",
|
||||
"AdminService", "Exception " + msg);
|
||||
return RPCUtil.getRemoteException(exception);
|
||||
|
|
Loading…
Reference in New Issue