https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-container-e70-144523545423-0003-01-000010-a-valid/m-p/95375#M8716 <P>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 ?</P> Wed, 14 Oct 2015 06:10:09 GMT jzhang 2015-10-14T06:10:09Z https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-container-e70-144523545423-0003-01-000010-a-valid/m-p/95375#M8716 <P>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 ?</P> Wed, 14 Oct 2015 06:10:09 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-container-e70-144523545423-0003-01-000010-a-valid/m-p/95375#M8716 jzhang 2015-10-14T06:10:09Z https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-container-e70-144523545423-0003-01-000010-a-valid/m-p/95376#M8717 <P>According to the Hadoop YARN API, here is the breakdown of the Container ID string:</P><P>"The format is container_e*epoch*_*clusterTimestamp*_*appId*_*attemptId*_*containerId*.</P><P>When epoch is larger than 0 (e.g. container_e17_1410901177871_0001_01_000005). *epoch* is increased when RM restarts or fails over.</P><P>When epoch is 0, epoch is omitted (e.g. container_1410901177871_0001_01_000005)."</P><P>To add more context, this was added by <A href="https://issues.apache.org/jira/browse/YARN-2562">YARN-2562</A> in Hadoop 2.6.0 as an improvement for readability of the containerId string. So, its an expected behavior.</P> Wed, 14 Oct 2015 06:41:37 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-container-e70-144523545423-0003-01-000010-a-valid/m-p/95376#M8717 deepesh1 2015-10-14T06:41:37Z