hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Templeton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6453) fairscheduler-statedump.log gets generated regardless of service
Date Thu, 20 Apr 2017 19:09:04 GMT

    [ https://issues.apache.org/jira/browse/YARN-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977275#comment-15977275

Daniel Templeton commented on YARN-6453:

Thanks, [~yufeigu].  Two nits: "Scheduler" is misspelled as "Schedule" and "FSSTATEDUMP" is
misspelled as "FSSATEDUMP".

> 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: 3.0.0-alpha3
>            Reporter: Allen Wittenauer
>            Assignee: Yufei Gu
>            Priority: Blocker
>         Attachments: YARN-6453.001.patch, YARN-6453.002.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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message