[YARN-8512] ATSv2 entities are not published to HBase from second attempt onwards

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0, 2.10.0, 3.2.0, 3.0.3
• Fix Version/s: 3.2.0, 3.1.1
• Labels: atsv2
• Target Version/s: 3.1.1
• Hadoop Flags: Reviewed
• Assignee: Rohith Sharma K S
• Reporter: Yesha Vora
• Created: 10/Jul/18 11:04
• Updated: 15/Feb/19 06:03
• Resolved: 11/Jul/18 06:58

Description

It is observed that if 1st attempt master container is died and 2nd attempt master container is launched in a NM where old containers are running but not master container.

Attempt	NM1	NM2	Action
attempt-1	master container i.e container-1-1	container-1-2	master container died
attempt-2	NA	container-1-2 and master container container-2-1	NA

In the above scenario, NM doesn't identifies flowContext and will get log below

2018-07-10 00:44:38,285 WARN  storage.HBaseTimelineWriterImpl (HBaseTimelineWriterImpl.java:write(170)) - Found null for one of: flowName=null appId=application_1531175172425_0001 userId=hbase clusterId=yarn-cluster . Not proceeding with writing to hbase
2018-07-10 00:44:38,560 WARN  storage.HBaseTimelineWriterImpl (HBaseTimelineWriterImpl.java:write(170)) - Found null for one of: flowName=null appId=application_1531175172425_0001 userId=hbase clusterId=yarn-cluster . Not proceeding with writing to hbase