hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7127) Merge yarn-native-service branch into trunk
Date Tue, 17 Oct 2017 18:35:00 GMT

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

Jian He commented on YARN-7127:
-------------------------------

[~aw], I would think this as another framework on YARN, with some core feature support from
YARN, primarily docker and scheduling. 
With that assumption, will a separate service subcommand make sense ? 
I'm just thinking even if the subcommands are merged with application, because the majority
of the options won't be applicable to generic apps. User end up having a larger set of options
and need to read through the docs to figure out which ones are applicable to service, or which
ones are applicable to all apps. 


> Merge yarn-native-service branch into trunk
> -------------------------------------------
>
>                 Key: YARN-7127
>                 URL: https://issues.apache.org/jira/browse/YARN-7127
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-7127.01.patch, YARN-7127.02.patch, YARN-7127.03.patch, YARN-7127.04.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message