[
https://issues.apache.org/jira/browse/YARN-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070730#comment-14070730
]
Zhijie Shen commented on YARN-2301:
-----------------------------------
bq. I think there would not be much useful by providing completed appAttemptId
for -list param and displaying some message or empty result.
As I mentioned before, the command is going to be applied to both RM and
timeline server. The latter is going to record the completed containers. -list
<appId> is able to list all the containers from the side of the timeline
server, and I hope it could work. So how about doing this for -list
<appId|appAttemptId> <additional opts>?
* appAttemptId: containers of a specific app attempt in RM/Timeline server (for
the case of RM, it is likely to show empty container list, but it's fine and it
is actually the current situation).
* appId with no additional opt: containers of the last(current) app attempt in
RM/Timeline server
* appId with -last: containers of the last(current) app attempt in RM/Timeline
server
*appId with -all: containers of all app attempts in RM/Timeline server
Does this make sense?
> 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)
