hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2301) Improve yarn container command
Date Mon, 21 Jul 2014 09:05:40 GMT

    [ https://issues.apache.org/jira/browse/YARN-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068332#comment-14068332

Naganarasimha G R commented on YARN-2301:

Hi [~jianhe] and [~zjshen]
                  I have fixed the first 3 but while working for the 4th one with [~zjshen]
bq.  4) May have an option to run as yarn container -list <appId>
i had to pick few alternatives so wanted opinion from you guys before i go forward
# Issue1 : As i understand this option should be in addition to ??yarn container -list <Application
Attempt ID>??, As its CLI we can't have polymorphic parameters,
	  so i thought of providing command like ??yarn container -list-forAppId <Application
ID>??. Is this option fine ? And please note GetContainersRequestProto api will be changed
# Issue2 : As [~zjshen] pointed out we need to take care for containers from Timeline server
flow also. For this i would suggest few options 
#* Option1: For the given AppID When application is still running (RM flow), Only show containers
for the current running application attempt irrespective of the earlier failure attempts.

When application is finished(Timeline server flow), Only show containers for the last attempt
of the application (whether its failed or succeded)
#* Option2: Introduce new additional parameter like ??-all??,??-last??. 
And let ??-last?? behave similar to option 1 and the default option and
for ??-all?? in both flows (RM and Timeline server flow) we display containers for each attempt.

> 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

View raw message