[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332142#comment-14332142 ]
Bartosz Ługowski commented on YARN-1621: ---------------------------------------- I had extracted {{yarn container}} method from ApplicationCLI to new file(ContainerCLI) and changed {{yarn container -list <Application Attempt ID>}} to {{yarn container -list <Application ID|Application Attempt ID>}}. Now container states filtering is done at server side(not at CLI, as suggested [~Naganarasimha]), and works for both: applications and application attempts. I didn't include changes in {{yarn.cmd}} because it brakes the patch(git can't apply it). > 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, > YARN-1621.4.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)