[
https://issues.apache.org/jira/browse/YARN-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625885#comment-13625885
]
Sandy Ryza commented on YARN-546:
---------------------------------
I checked in the code and that appears to be correct. The event log in hadoop
1 was broken for a long time until a recent issue I fixed, which leads me to
suspect that nobody has really been using it. I've also heard complaints that,
because an entry is logged for each node update, it contains too much
information and is not very helpful. I think we should consider removing it in
Hadoop 2.0 entirely.
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
