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

Naganarasimha G R commented on YARN-2808:
-----------------------------------------

Hi [~GWong]
   Earlier idea was the same, but i feel there might be lot of differences for 
supporting "yarn container" command for both applicationID and application 
attemptID with -list option itself, so as suggested by JianHe in 
[YARN-2301|https://issues.apache.org/jira/browse/YARN-2301?focusedCommentId=14070512&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14070512],
 i thought of splitting as follows.
# YARN-2301 : for first 3 small issues 
# new jira for supporting "yarn container" command for both applicationID and 
application attemptID 
# listing of all containers even for running and completed apps as part of 
yarn-1794 (similar to the current issue will confirm with Mayank and finalize 
it )

Have already been working on this but was waiting for level DB based Timeline 
server to be committed to get all the containers from timeline server itself 
which will resolve most of the issues of  "yarn container" command.

> yarn client tool can not list app_attempt's container info correctly
> --------------------------------------------------------------------
>
>                 Key: YARN-2808
>                 URL: https://issues.apache.org/jira/browse/YARN-2808
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: client
>            Reporter: Gordon Wang
>            Assignee: Naganarasimha G R
>
> When enabling timeline server, yarn client can not list the container info 
> for a application attempt correctly.
> Here is the reproduce step.
> # enabling yarn timeline server
> # submit a MR job
> # after the job is finished. use yarn client to list the container info of 
> the app attempt.
> Then, since the RM has cached the application's attempt info, the output show 
> {noformat}
> [hadoop@localhost hadoop-3.0.0-SNAPSHOT]$ ./bin/yarn container -list 
> appattempt_1415168250217_0001_000001
> 14/11/05 01:19:15 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> 14/11/05 01:19:15 INFO impl.TimelineClientImpl: Timeline service address: 
> http://0.0.0.0:8188/ws/v1/timeline/
> 14/11/05 01:19:16 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 14/11/05 01:19:16 INFO client.AHSProxy: Connecting to Application History 
> server at /0.0.0.0:10200
> Total number of containers :0
>                   Container-Id                  Start Time             Finish 
> Time                   State                    Host                          
>       LOG-URL
> {noformat}
> But if the rm is restarted, client can fetch the container info from timeline 
> server correctly.
> {noformat}
> [hadoop@localhost hadoop-3.0.0-SNAPSHOT]$ ./bin/yarn container -list 
> appattempt_1415168250217_0001_000001
> 14/11/05 01:21:06 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> 14/11/05 01:21:06 INFO impl.TimelineClientImpl: Timeline service address: 
> http://0.0.0.0:8188/ws/v1/timeline/
> 14/11/05 01:21:06 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 14/11/05 01:21:06 INFO client.AHSProxy: Connecting to Application History 
> server at /0.0.0.0:10200
> Total number of containers :4
>                   Container-Id                  Start Time             Finish 
> Time                   State                    Host                          
>       LOG-URL
> container_1415168250217_0001_01_000001               1415168318376           
> 1415168349896                COMPLETE    localhost.localdomain:47024     
> http://0.0.0.0:8188/applicationhistory/logs/localhost.localdomain:47024/container_1415168250217_0001_01_000001/container_1415168250217_0001_01_000001/hadoop
> container_1415168250217_0001_01_000002               1415168326399           
> 1415168334858                COMPLETE    localhost.localdomain:47024     
> http://0.0.0.0:8188/applicationhistory/logs/localhost.localdomain:47024/container_1415168250217_0001_01_000002/container_1415168250217_0001_01_000002/hadoop
> container_1415168250217_0001_01_000003               1415168326400           
> 1415168335277                COMPLETE    localhost.localdomain:47024     
> http://0.0.0.0:8188/applicationhistory/logs/localhost.localdomain:47024/container_1415168250217_0001_01_000003/container_1415168250217_0001_01_000003/hadoop
> container_1415168250217_0001_01_000004               1415168335825           
> 1415168343873                COMPLETE    localhost.localdomain:47024     
> http://0.0.0.0:8188/applicationhistory/logs/localhost.localdomain:47024/container_1415168250217_0001_01_000004/container_1415168250217_0001_01_000004/hadoop
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to