Support Questions

Find answers, ask questions, and share your expertise

Is container_e70_144523545423_0003_01_000010 a valid containerId ?

avatar
Super Collaborator

I am not sure why e70 is in the part of containerId, I do see it in a HDP 2.3 environment. Is this expected or a known issue ?

1 ACCEPTED SOLUTION

avatar

According to the Hadoop YARN API, here is the breakdown of the Container ID string:

"The format is container_e*epoch*_*clusterTimestamp*_*appId*_*attemptId*_*containerId*.

When epoch is larger than 0 (e.g. container_e17_1410901177871_0001_01_000005). *epoch* is increased when RM restarts or fails over.

When epoch is 0, epoch is omitted (e.g. container_1410901177871_0001_01_000005)."

To add more context, this was added by YARN-2562 in Hadoop 2.6.0 as an improvement for readability of the containerId string. So, its an expected behavior.

View solution in original post

1 REPLY 1

avatar

According to the Hadoop YARN API, here is the breakdown of the Container ID string:

"The format is container_e*epoch*_*clusterTimestamp*_*appId*_*attemptId*_*containerId*.

When epoch is larger than 0 (e.g. container_e17_1410901177871_0001_01_000005). *epoch* is increased when RM restarts or fails over.

When epoch is 0, epoch is omitted (e.g. container_1410901177871_0001_01_000005)."

To add more context, this was added by YARN-2562 in Hadoop 2.6.0 as an improvement for readability of the containerId string. So, its an expected behavior.