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 Tue, 05 Aug 2014 01:23:12 GMT

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

Naganarasimha G R commented on YARN-2301:

Hi [~zjshen],
   I believe the existing working of 
bq. yarn container -list <appAttemptID>
itself is not proper (wrt  YARN-1794) and once all the data is taken from time line server
it would make proper sense for the end user.
End user should not bother its coming from AHS/Timeline/RM and result should be list of all
containers for the given attempt or app ID.
I have the code for the command
bd.yarn container -list <appAttemptID/appID>
but i feel it would not be complete until timeline integration is done and users of this command
will again get confused if given with half feature
So my pick would be to your second option as new jira i.e 
bq. *yarn container -list <appAttemptID/appID>*
but if you see timeline server intergration will be delayed then we can discuss what part
of the command could be taken and the behavior of it.
Also i would like to fix YARN-1794-??show all containers when application is finished from
AHS instead of no containers from RM?? 
(again here too . i would like to fix the bug after timeline integration, so that list of
all containers for the given attempt or app ID irrespective of the app state )
Please provide your opinion.

> 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