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 0443B1064C for ; Thu, 14 Nov 2013 12:09:31 +0000 (UTC) Received: (qmail 87455 invoked by uid 500); 14 Nov 2013 12:09:29 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 86775 invoked by uid 500); 14 Nov 2013 12:09:24 -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 86718 invoked by uid 99); 14 Nov 2013 12:09:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Nov 2013 12:09:21 +0000 Date: Thu, 14 Nov 2013 12:09:21 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1383) Remove node updates from the Fair Scheduler event log 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-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822356#comment-13822356 ] Karthik Kambatla commented on YARN-1383: ---------------------------------------- Sorry for the delay, somehow skipped my mind. I remember using the FS event log when debugging at least 4 production issues. On one such occasion, when jobs/tasks were surprisingly slow, I remember using the FS event log to check what nodes the tasks were being assigned to and if those nodes were heartbeating at all. The issue turned out to be node-specific. It might be possible to arrive at the same conclusion through other means, FS event log makes it super-easy to debug these situations. I completely understand it is too expensive to log these messages all the time. However, it would be nice to at least log these at a trace level. When debugging an issue requiring this, we can always turn on trace-level logging. > Remove node updates from the Fair Scheduler event log > ----------------------------------------------------- > > Key: YARN-1383 > URL: https://issues.apache.org/jira/browse/YARN-1383 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler > Affects Versions: 2.2.0 > Reporter: Sandy Ryza > Assignee: Sandy Ryza > Attachments: YARN-1383.patch > > > Writing out a line whenever a node heartbeats is not useful and just too much. -- This message was sent by Atlassian JIRA (v6.1#6144)