Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 34C1E200AC9 for ; Sun, 1 May 2016 09:55:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 336561609A9; Sun, 1 May 2016 09:55:15 +0200 (CEST) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7A5191609AA for ; Sun, 1 May 2016 09:55:14 +0200 (CEST) Received: (qmail 44681 invoked by uid 500); 1 May 2016 07:55:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 44582 invoked by uid 99); 1 May 2016 07:55:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 May 2016 07:55:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 003D32C1F61 for ; Sun, 1 May 2016 07:55:13 +0000 (UTC) Date: Sun, 1 May 2016 07:55:12 +0000 (UTC) From: "Varun Vasudev (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4969) Fix more loggings in CapacityScheduler MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 01 May 2016 07:55:15 -0000 [ https://issues.apache.org/jira/browse/YARN-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265656#comment-15265656 ] Varun Vasudev commented on YARN-4969: ------------------------------------- [~leftnoteasy] - you think it makes sense to just move all the capacity scheduler logging into it's own file? > Fix more loggings in CapacityScheduler > -------------------------------------- > > Key: YARN-4969 > URL: https://issues.apache.org/jira/browse/YARN-4969 > Project: Hadoop YARN > Issue Type: Bug > Components: capacity scheduler > Reporter: Wangda Tan > Assignee: Wangda Tan > Attachments: YARN-4969.1.patch > > > YARN-3966 did logging cleanup for Capacity Scheduler before, however, there're some loggings we need to improvement: > Container allocation / complete / reservation / un-reserve messages for every hierarchy (app/leaf/parent-queue) should be printed at INFO level: > I'm debugging one issue that root queue's resource usage could be negative, it is very hard to reproduce, so we cannot enable debug logging since RM start, size of log cannot be fit in a single disk. > Existing CS prints INFO message when container cannot be allocated, such as re-reservation / node heartbeat, etc. we should avoid printing such message at INFO level. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org