You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Tsuyoshi Ozawa (JIRA)" <ji...@apache.org> on 2015/02/26 16:58:04 UTC

[jira] [Updated] (YARN-3255) RM, NM, JobHistoryServer, and WebAppProxyServer's main() should support generic options

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

Tsuyoshi Ozawa updated YARN-3255:
---------------------------------
    Summary: RM, NM, JobHistoryServer, and WebAppProxyServer's main() should support generic options  (was: RM and NM main() should support generic options)

> RM, NM, JobHistoryServer, and WebAppProxyServer's main() should support generic options
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-3255
>                 URL: https://issues.apache.org/jira/browse/YARN-3255
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager, resourcemanager
>    Affects Versions: 2.5.0
>            Reporter: Konstantin Shvachko
>            Assignee: Konstantin Shvachko
>         Attachments: YARN-3255-01.patch, YARN-3255-02.patch
>
>
> Currently {{ResourceManager.main()}} and {{NodeManager.main()}} ignore generic options, like {{-conf}} and {{-fs}}. It would be good to have the ability to pass generic options in order to specify configuration files or the NameNode location, when the services start through {{main()}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)