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