[
https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314997#comment-14314997
]
Vinod Kumar Vavilapalli commented on YARN-1621:
-----------------------------------------------
Thanks for working on this Bartosz. Quick comments on the patch:
- listcontainers -> list-containers
- Add a negative test for pre-running applications
Overall, the CLI is pretty badly organized, and this patch is making it worse.
We have
- applicationattempt -list applicationId: Lists appattempts of an app
- container -list attemptId: Lists containers of an attempt
- application -list: List all apps
I don't like this, but it is what we have. For this patch, we can continue this
scheme and put a "container -list appattemptid". And may be a create different
set of commands which make the listing work backwards in a separate effort.
> Add CLI to list rows of <task attempt ID, container ID, host of container,
> state of container>
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-1621
> URL: https://issues.apache.org/jira/browse/YARN-1621
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.2.0
> Reporter: Tassapol Athiapinya
> Assignee: Bartosz Ługowski
> Fix For: 2.7.0
>
> Attachments: YARN-1621.1.patch, YARN-1621.2.patch, YARN-1621.3.patch
>
>
> As more applications are moved to YARN, we need generic CLI to list rows of
> <task attempt ID, container ID, host of container, state of container>. Today
> if YARN application running in a container does hang, there is no way to find
> out more info because a user does not know where each attempt is running in.
> For each running application, it is useful to differentiate between
> running/succeeded/failed/killed containers.
>
> {code:title=proposed yarn cli}
> $ yarn application -list-containers -applicationId <appId> [-containerState
> <state of container>]
> where containerState is optional filter to list container in given state only.
> <container state> can be running/succeeded/killed/failed/all.
> A user can specify more than one container state at once e.g. KILLED,FAILED.
> <task attempt ID> <container ID> <host of container> <state of container>
> {code}
> CLI should work with running application/completed application. If a
> container runs many task attempts, all attempts should be shown. That will
> likely be the case of Tez container-reuse application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
