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 603031073B for ; Mon, 31 Mar 2014 18:23:44 +0000 (UTC) Received: (qmail 16339 invoked by uid 500); 31 Mar 2014 18:23:34 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 16283 invoked by uid 500); 31 Mar 2014 18:23:31 -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 16076 invoked by uid 99); 31 Mar 2014 18:23:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2014 18:23:16 +0000 Date: Mon, 31 Mar 2014 18:23:16 +0000 (UTC) From: "Jian He (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-1892) Excessive logging in RM 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-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1892: -------------------------- Attachment: YARN-1892.1.patch Simple patch to clean some CS loggings. These logs will become more excessive if async scheduling is enabled, log per 5ms cycle by default. Move a few redundant logs regarding container reservation to debug level. Fix a few log formats and contents. > Excessive logging in RM > ----------------------- > > Key: YARN-1892 > URL: https://issues.apache.org/jira/browse/YARN-1892 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Siddharth Seth > Assignee: Jian He > Priority: Minor > Attachments: YARN-1892.1.patch > > > Mostly in the CS I believe > {code} > INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt: Application application_1395435468498_0011 reserved container container_1395435468498_0011_01_000213 on node host: #containers=5 available=4096 used=20960, currently has 1 at priority 4; currentReservation 4096 > {code} > {code} > INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: hive2 usedResources: clusterResources: currentCapacity 0.25 required potentialNewCapacity: 0.255 ( max-capacity: 0.25) > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)