[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230587#comment-14230587 ]
Hadoop QA commented on YARN-1621: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12684481/YARN-1621.2.patch against trunk revision 2b30fb1. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client: org.apache.hadoop.yarn.client.TestResourceTrackerOnHA org.apache.hadoop.yarn.client.TestApplicationClientProtocolOnHA {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/5964//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5964//console This message is automatically generated. > 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 > Fix For: 2.7.0 > > Attachments: YARN-1621.1.patch, YARN-1621.2.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)