[
https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315576#comment-14315576
]
Naganarasimha G R commented on YARN-1621:
-----------------------------------------
Thanks for working on this [~noddi] and earlier [~jianhe] had raised a similar
topic in YARN-2301 (4th point) which was not finished as part of 2301 and i
had started working on it and had plans to raise this issue in a separate jira,
As the purpose of this jira is similar to that, thought of sharing some points
# In one of the YARN-2301 [comment|
https://issues.apache.org/jira/browse/YARN-2301?focusedCommentId=14070730&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14070730],
[~zjshen] had suggested
{quote}
yarn container -list <appId|appAttemptId> <additional opts>?
appAttemptId: containers of a specific app attempt
appId with no additional opt: containers of the last(current) app attempt
appId with -last: containers of the last(current) app attempt
*appId with -all: containers of all app attempts
{quote}
IMHO it would better to support the listing of containers for a application as
part of containers(yarn container -list) itself. and further we can think of
adding states to this command.
# When working with MR apps with large number of tasks would it be good to
process filters on containers @ the server side than the client side? or at
least would it be better to get it done @ the YARNclient level where in not
only the CLI even RPC will be able to get the benefit of these modifications
# "Start Time", "Finish Time", "LOG-URL" will also be usefull to be listed for
each container (would get handled if we make it as part of yarn container -list
command)
[~vinodkv], [~noddi],[~jianhe] & [~zjshen] please provide your opinion on the
approach to list the containers for a application
If required to be supported in the approach as mentioned by Zhijie shen, I
would like to work on it as i have already completed with half of the
modifications.
Few other minor comments :
* {{+ "of -containerState to filter containers based "}}
should be {{-containerStates }}
> 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)
