- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Is container_e70_144523545423_0003_01_000010 a valid containerId ?
- Labels:
-
Apache YARN
Created ‎10-13-2015 11:10 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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 ?
Created ‎10-13-2015 11:41 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Created ‎10-13-2015 11:41 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
