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 7217B10977 for ; Thu, 5 Dec 2013 17:16:40 +0000 (UTC) Received: (qmail 54173 invoked by uid 500); 5 Dec 2013 17:16:39 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 53990 invoked by uid 500); 5 Dec 2013 17:16:39 -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 53886 invoked by uid 99); 5 Dec 2013 17:16:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 17:16:38 +0000 Date: Thu, 5 Dec 2013 17:16:38 +0000 (UTC) From: "Sandy Ryza (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-546) mapred.fairscheduler.eventlog.enabled removed from Hadoop 2.0 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-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840297#comment-13840297 ] Sandy Ryza commented on YARN-546: --------------------------------- bq. Also, in many other cases (RM etc.), we have these methods or config-accesses in the class that uses them and not in *Configuration. Any reason to not follow the same? Agreed that it's non-standard compared to the rest of YARN, but I'm following the convention used by the other Fair Scheduler configs. Will upload a patch that changes "get" to is and makes those constants public. > mapred.fairscheduler.eventlog.enabled removed from Hadoop 2.0 > ------------------------------------------------------------- > > Key: YARN-546 > URL: https://issues.apache.org/jira/browse/YARN-546 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler > Affects Versions: 2.0.3-alpha > Reporter: Lohit Vijayarenu > Assignee: Sandy Ryza > Attachments: YARN-546.1.patch, YARN-546.patch > > > Hadoop 1.0 supported an option to turn on/off FairScheduler event logging using mapred.fairscheduler.eventlog.enabled. In Hadoop 2.0, it looks like this option has been removed (or not ported?) which causes event logging to be enabled by default and there is no way to turn it off. -- This message was sent by Atlassian JIRA (v6.1#6144)