Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 28 Nov 2013 17:44:37 +0000 (UTC)
From: "Sandy Ryza (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12640924.1365137259242.44921.1385660677948@arcas>
In-Reply-To: <JIRA.12640924.1365137259242@arcas>
References: <JIRA.12640924.1365137259242@arcas>
Subject: [jira] [Reopened] (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


     [ https://issues.apache.org/jira/browse/YARN-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandy Ryza reopened YARN-546:
-----------------------------

      Assignee: Sandy Ryza

I've spoken to a few people that still see the event log as valuable.  Independent of what we choose to do in YARN-1383, we should make disabling it an option.  Will post a patch here soon.

I'm going to put the option into the allocations file instead of as a yarn config so that it can be turned off and on.

> 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
>
>
> 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)