Naganarasimha G R commented on YARN-2301:

Hi All,
        Sorry for the break, i was in transit away from my home location and 
hence was not able to put more effort on this issue.
Based on the initial understanding of the interface and commands documentation, 
i thought the suggestions mentioned by [~zjshen] is feasible, but while coding 
and testing i came to realise 
that this command (or existing command: yarn container -list <appAttemptID>) 
behaves differently when it hits RM and AHS.
RM provides only live running containers and only when RM doesnt have the 
applicationid (or applicationAttemptId) it throws exception and only then AHS 
is contacted to retreive all the containers.
There is already an issue raised for YARN-1794(Yarn CLI only shows running 
containers for Running Applications) 
so i would like to fix the first 3 points in this jira and open a new jira for 
the 4th point and make that dependent on  YARN-1794. And once YARN-1794 is 
taken care then would like to finish the 4th point
[~zjshen],[~sunilg],[~devaraj.k] & [~jianhe] 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

Reply via email to