Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6B26210122 for ; Tue, 11 Mar 2014 23:58:52 +0000 (UTC) Received: (qmail 79325 invoked by uid 500); 11 Mar 2014 23:58:50 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 79163 invoked by uid 500); 11 Mar 2014 23:58:49 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 79035 invoked by uid 99); 11 Mar 2014 23:58:47 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2014 23:58:47 +0000 Date: Tue, 11 Mar 2014 23:58:47 +0000 (UTC) From: "Sietse T. Au (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1022) Unnecessary INFO logs in AMRMClientAsync MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931178#comment-13931178 ] Sietse T. Au commented on YARN-1022: ------------------------------------ The patch is targeting the wrong LOG.info, it should be the LOG.info caused by "AMRMClientAsyncImpl.java:275", as we see in the logs in the description. LOG.info("Interrupted while waiting for queue", ex); -> LOG.debug("Interrupted while waiting for queue", ex); on line 277. > 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 > Assignee: haosdent > Priority: Trivial > Labels: newbie > Fix For: 2.3.0 > > Attachments: YARN-1022.patch > > > 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 was sent by Atlassian JIRA (v6.2#6252)