Yesha Vora created YARN-4502:

             Summary: Sometimes Two AM containers get launched
                 Key: YARN-4502
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Yesha Vora
            Priority: Critical

Scenario : 
* set = 2
* start dshell application
 yarn  org.apache.hadoop.yarn.applications.distributedshell.Client -jar 
-attempt_failures_validity_interval 60000 -shell_command "sleep 150" 
-num_containers 16
* Kill AM pid
* Print container list for 2nd attempt
yarn container -list appattempt_1450825622869_0001_000002
INFO impl.TimelineClientImpl: Timeline service address: 
INFO client.RMProxy: Connecting to ResourceManager at xxx/<port>
Total number of containers :2
Container-Id                 Start Time             Finish Time                 
  State                    Host       Node Http Address                         
container_e12_1450825622869_0001_02_000002 Tue Dec 22 23:07:35 +0000 2015       
            N/A                 RUNNING    xxx:25454       http://xxx:8042 
container_e12_1450825622869_0001_02_000001 Tue Dec 22 23:07:34 +0000 2015       
            N/A                 RUNNING    xxx:25454       http://xxx:8042 
* look for new AM pid 

Here, 2nd AM container was suppose to be started on  
container_e12_1450825622869_0001_02_000001. But AM was not launched on 
container_e12_1450825622869_0001_02_000001. It was in AQUIRED state. 
On other hand, container_e12_1450825622869_0001_02_000002 got the AM running. 

Expected behavior: RM should not start 2 containers for starting AM

This message was sent by Atlassian JIRA

Reply via email to