[YARN-8330] Avoid publishing reserved container to ATS from RM

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 3.2.0, 3.1.2
• Component/s: yarn-native-services
• Assignee: Suma Shivaprasad
• Reporter: Yesha Vora
• Created: 19/May/18 20:22
• Updated: 18/Mar/19 14:00
• Resolved: 25/Jul/18 22:54

Description

Steps:
launch Hbase tarball app
list containers for hbase tarball app

/usr/hdp/current/hadoop-yarn-client/bin/yarn container -list appattempt_1525463491331_0006_000001
WARNING: YARN_LOG_DIR has been replaced by HADOOP_LOG_DIR. Using value of YARN_LOG_DIR.
WARNING: YARN_LOGFILE has been replaced by HADOOP_LOGFILE. Using value of YARN_LOGFILE.
WARNING: YARN_PID_DIR has been replaced by HADOOP_PID_DIR. Using value of YARN_PID_DIR.
WARNING: YARN_OPTS has been replaced by HADOOP_OPTS. Using value of YARN_OPTS.
18/05/04 22:36:11 INFO client.AHSProxy: Connecting to Application History server at xxx/xxx:10200
18/05/04 22:36:11 INFO client.ConfiguredRMFailoverProxyProvider: Failing over to rm2
Total number of containers :5
Container-Id            Start Time             Finish Time                   State                    Host       Node Http Address                                LOG-URL
container_e06_1525463491331_0006_01_000002    Fri May 04 22:34:26 +0000 2018                   N/A                 RUNNING    xxx:25454  http://xxx:8042    http://xxx:8042/node/containerlogs/container_e06_1525463491331_0006_01_000002/hrt_qa
2018-05-04 22:36:11,216|INFO|MainThread|machine.py:167 - run()||GUID=0169fa41-d1c5-4b43-85bf-c3e9f2682398|container_e06_1525463491331_0006_01_000003    Fri May 04 22:34:26 +0000 2018                   N/A                 RUNNING    xxx:25454  http://xxx:8042    http://xxx:8042/node/containerlogs/container_e06_1525463491331_0006_01_000003/hrt_qa
2018-05-04 22:36:11,217|INFO|MainThread|machine.py:167 - run()||GUID=0169fa41-d1c5-4b43-85bf-c3e9f2682398|container_e06_1525463491331_0006_01_000001    Fri May 04 22:34:15 +0000 2018                   N/A                 RUNNING    xxx:25454  http://xxx:8042    http://xxx:8042/node/containerlogs/container_e06_1525463491331_0006_01_000001/hrt_qa
2018-05-04 22:36:11,217|INFO|MainThread|machine.py:167 - run()||GUID=0169fa41-d1c5-4b43-85bf-c3e9f2682398|container_e06_1525463491331_0006_01_000005    Fri May 04 22:34:56 +0000 2018                   N/A                 RUNNING    xxx:25454  http://xxx:8042    http://xxx:8042/node/containerlogs/container_e06_1525463491331_0006_01_000005/hrt_qa
2018-05-04 22:36:11,218|INFO|MainThread|machine.py:167 - run()||GUID=0169fa41-d1c5-4b43-85bf-c3e9f2682398|container_e06_1525463491331_0006_01_000004    Fri May 04 22:34:56 +0000 2018                   N/A                    null    xxx:25454  http://xxx:8042    http://xxx:8188/applicationhistory/logs/xxx:25454/container_e06_1525463491331_0006_01_000004/container_e06_1525463491331_0006_01_000004/hrt_qa

Total expected containers = 4 ( 3 components container + 1 am). Instead, RM is listing 5 containers.
container_e06_1525463491331_0006_01_000004 is in null state.
Yarn service utilized container 02, 03, 05 for component. There is no log available in NM & AM related to container 04. Only one line in RM log is printed

2018-05-04 22:34:56,618 INFO  rmcontainer.RMContainerImpl (RMContainerImpl.java:handle(489)) - container_e06_1525463491331_0006_01_000004 Container Transitioned from NEW to RESERVED

Issue Links

• causes: YARN-9396 YARN_RM_CONTAINER_CREATED published twice to ATS
• duplicates: YARN-3884 App History status not updated when RMContainer transitions from RESERVED to KILLED