[
https://issues.apache.org/jira/browse/YARN-7127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209865#comment-16209865
]
Allen Wittenauer commented on YARN-7127:
----------------------------------------
bq. With that assumption, will a separate service subcommand make sense ?
Let's test that assumption.
Would a user be able to replace the bundled AM with their own and retain all of
the functionality?
If someone wanted to replicate the native services features, would they be able
to do it using only Public APIs?
bq. 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.
They'd have to do this anyway whether the commands are spit apart or not. In
fact, it's worse if they are split because now there are two sets of commands
that work different and apply to different applications. e.g., I can't use the
proposed 'yarn service' command to stop MapReduce.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
