[YARN-5094] some YARN container events have timestamp of -1

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.9.0, 3.0.0
• Fix Version/s: 3.1.0, 2.9.1, 3.0.1
• Labels: YARN-5355
• Hadoop Flags: Reviewed
• Assignee: Haibo Chen
• Reporter: Sangjin Lee
• Created: 16/May/16 22:53
• Updated: 13/Apr/18 17:06
• Resolved: 19/Jan/18 18:51

Description

Some events in the YARN container entities have timestamp of -1. The RM-generated container events have proper timestamps. It appears that it's the NM-generated events that have -1: YARN_CONTAINER_CREATED, YARN_CONTAINER_FINISHED, YARN_NM_CONTAINER_LOCALIZATION_FINISHED, YARN_NM_CONTAINER_LOCALIZATION_STARTED.

In the YARN container page,

{
id: "YARN_CONTAINER_CREATED",
timestamp: -1,
info: { }
},
{
id: "YARN_CONTAINER_FINISHED",
timestamp: -1,
info: {
YARN_CONTAINER_EXIT_STATUS: 0,
YARN_CONTAINER_STATE: "RUNNING",
YARN_CONTAINER_DIAGNOSTICS_INFO: ""
}
},
{
id: "YARN_NM_CONTAINER_LOCALIZATION_FINISHED",
timestamp: -1,
info: { }
},
{
id: "YARN_NM_CONTAINER_LOCALIZATION_STARTED",
timestamp: -1,
info: { }
}

I think the data itself is OK, but the values are not being populated in the REST output?

Issue Links

• is related to: YARN-5169 most YARN events have timestamp of -1