[
https://issues.apache.org/jira/browse/YARN-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066195#comment-14066195
]
Zhijie Shen commented on YARN-2301:
-----------------------------------
bq. As attempt Id is not shown on console, this is easier for user to just copy
the appId and run it, may also be useful for container-preserving AM restart.
You can run yarn appattempt to get the attempt. Anyway it's arguable if it is
user friendly or not. Given adding a function, I vote for yarn container -list
<appId>
One more comment. “yarn container” can source the container information either
from RM or from timeline server. When making the changes, please make sure the
both sides are changed consistently
> Improve yarn container command
> ------------------------------
>
> Key: YARN-2301
> URL: https://issues.apache.org/jira/browse/YARN-2301
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Jian He
> Assignee: Naganarasimha G R
> Labels: usability
>
> While running yarn container -list <Application Attempt ID> command, some
> observations:
> 1) the scheme (e.g. http/https ) before LOG-URL is missing
> 2) the start-time is printed as milli seconds (e.g. 1405540544844). Better to
> print as time format.
> 3) finish-time is 0 if container is not yet finished. May be "N/A"
> 4) May have an option to run as yarn container -list <appId> OR yarn
> application -list-containers <appId> also.
> As attempt Id is not shown on console, this is easier for user to just copy
> the appId and run it, may also be useful for container-preserving AM
> restart.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
