Details
-
Bug
-
Status: Resolved
-
Trivial
-
Resolution: Fixed
-
2.7.3
-
None
-
Reviewed
Description
Logs like the following should be debug or else every legitimate stop causes unnecessary exception traces in the logs.
2013-08-03 20:01:34,460 INFO [AMRM Callback Handler Thread] org.apache.hadoop.yarn.client.api.async.impl.AMRMClientAsyncImpl: Interrupted while waiting for queue java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer. java:1961) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1996) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399) at org.apache.hadoop.yarn.client.api.async.impl.AMRMClientAsyncImpl$CallbackHandlerThread.run(AMRMClientAsyncImpl.java:275)
Attachments
Attachments
Issue Links
- is a clone of
-
YARN-1022 Unnecessary INFO logs in AMRMClientAsync
- Closed