[
https://issues.apache.org/jira/browse/YARN-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977583#comment-15977583
]
Hudson commented on YARN-6453:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11616 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11616/])
YARN-6453. fairscheduler-statedump.log gets generated regardless of (templedf:
rev f356f0f4cf22efdc920c2a4be2b4b6a5fc4c3e3c)
* (edit) hadoop-common-project/hadoop-common/src/main/conf/log4j.properties
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/FairScheduler.md
> fairscheduler-statedump.log gets generated regardless of service
> ----------------------------------------------------------------
>
> Key: YARN-6453
> URL: https://issues.apache.org/jira/browse/YARN-6453
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler, scheduler
> Affects Versions: 2.9.0, 3.0.0-alpha3
> Reporter: Allen Wittenauer
> Assignee: Yufei Gu
> Priority: Blocker
> Fix For: 2.9.0, 3.0.0-alpha3
>
> Attachments: YARN-6453.001.patch, YARN-6453.002.patch,
> YARN-6453.003.patch, YARN-6453.004.patch
>
>
> An empty fairscheduler-statedump.log is getting generated despite fair share
> not being the configured scheduler and for every service. i.e., starting a
> namenode will also generate this file. For single node test installations,
> this is a major problem if the services are started as different users and/or
> with secure daemons.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
