You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2013/09/25 01:32:15 UTC
[jira] [Updated] (YARN-1022) Unnecessary INFO logs in
AMRMClientAsync
[ https://issues.apache.org/jira/browse/YARN-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated YARN-1022:
--------------------------------
Fix Version/s: (was: 2.1.1-beta)
2.1.2-beta
> Unnecessary INFO logs in AMRMClientAsync
> ----------------------------------------
>
> Key: YARN-1022
> URL: https://issues.apache.org/jira/browse/YARN-1022
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bikas Saha
> Priority: Minor
> Labels: newbie
> Fix For: 2.1.2-beta
>
>
> Logs like the following should be debug or else every legitimate stop causes unnecessary exception traces in the logs.
> 464 2013-08-03 20:01:34,459 INFO [AMRM Heartbeater thread] org.apache.hadoop.yarn.client.api.async.impl.AMRMClientAsyncImpl: Heartbeater interrupted
> 465 java.lang.InterruptedException: sleep interrupted
> 466 at java.lang.Thread.sleep(Native Method)
> 467 at org.apache.hadoop.yarn.client.api.async.impl.AMRMClientAsyncImpl$HeartbeatThread.run(AMRMClientAsyncImpl.java:249)
> 468 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
> 469 java.lang.InterruptedException
> 470 at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer. java:1961)
> 471 at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1996)
> 472 at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
> 473 at org.apache.hadoop.yarn.client.api.async.impl.AMRMClientAsyncImpl$CallbackHandlerThread.run(AMRMClientAsyncImpl.java:275)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira