hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2301) Improve yarn container command
Date Mon, 21 Jul 2014 17:12:41 GMT

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

Zhijie Shen commented on YARN-2301:

bq. 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,

How about having -list only, and then parsing whether the given id is app id or app attempt

bq. Issue2 : As Zhijie Shen pointed out we need to take care for containers from Timeline
server flow also. For this i would suggest few options

Option 2 sounds more attractive to me if it doesn't introduce too much complexity.

>[~jianhe], I don't tracking the recent scheduler changes. Is it able to show the containers
of previous app attempt, or the finished containers of the current app attempt? Previously,
the container is removed from the scheduler if it is finished.

If so, -all can only work for the application in the timeline server but not the running app
in RM.

> 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