[
https://issues.apache.org/jira/browse/YARN-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16324156#comment-16324156
]
Billie Rinaldi commented on YARN-7724:
--------------------------------------
The changes to ApplicationCLI look good. The changes to ServiceClient and
AppAdminClient are no longer needed. The usage statement should also be
updated. Here is the current usage; I suggest changing status to have something
similar to the stop command:
{noformat}
-status <Application ID> Prints the status of the
application.
-stop <Application Name or ID> Stops application gracefully
(may be started again later). If
name is provided, appType must
be provided unless it is the
default yarn-service. If ID is
provided, the appType will be
looked up. Supports -appTypes
option to specify which client
implementation to use.
{noformat}
Except for the part about "If ID is provided, the appType will be looked up,"
because that isn't true for status. See ApplicationCLI.java#L140-L141 and
ApplicationCLI.java#L193. When usage is updated,
TestYarnCLI.createApplicationCLIHelpMessage and YarnCommands.md will also need
to be updated.
> yarn application status should support application name
> -------------------------------------------------------
>
> Key: YARN-7724
> URL: https://issues.apache.org/jira/browse/YARN-7724
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn-native-services
> Reporter: Yesha Vora
> Assignee: Jian He
> Attachments: YARN-7724.01.patch, YARN-7724.02.patch,
> YARN-7724.03.patch
>
>
> Yarn Service application are tied with app name. Thus, yarn application
> -status should be able to take yarn service name as argument such as
> yarn application -status <yarnservice name>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
