[
https://issues.apache.org/jira/browse/YARN-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321360#comment-16321360
]
Gour Saha commented on YARN-7724:
---------------------------------
Suggestion:
I think we should leave the output of "yarn app -status <appId>" to yarn
generic status only. This will keep backward compatibility, and avoid existing
client-side tools to possibly fail while parsing the output. If the <appId> is
that of a service, clients can call "yarn app -status <appName>" again to get
the service json status.
Note, for a service, if app name is not known but app id is known, clients can
call the first cli and get the <appName> which is printed in the yarn generic
status and subsequently call the second cli. Also, for service status, we
should print the json only. No need to print the string header "Detailed
Application Status :" and make it an invalid json.
> 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
> Attachments: YARN-7724.01.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]
