[
https://issues.apache.org/jira/browse/YARN-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524329#comment-14524329
]
Wangda Tan commented on YARN-3017:
----------------------------------
I can see this behavior in latest trunk as well:
{code}
2015-05-01 00:53:44,575 INFO attempt.RMAppAttemptImpl
(RMAppAttemptImpl.java:handle(793)) - appattempt_1430441527236_0001_000001
State change from SUBMITTED to SCHEDULED
2015-05-01 00:53:44,928 INFO rmcontainer.RMContainerImpl
(RMContainerImpl.java:handle(394)) - container_1430441527236_0001_01_000001
Container Transitioned from NEW to ALLOCATED
{code}
It's better to make them consistent
> ContainerID in ResourceManager Log Has Slightly Different Format From
> AppAttemptID
> ----------------------------------------------------------------------------------
>
> Key: YARN-3017
> URL: https://issues.apache.org/jira/browse/YARN-3017
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: MUFEED USMAN
> Priority: Minor
>
> Not sure if this should be filed as a bug or not.
> In the ResourceManager log in the events surrounding the creation of a new
> application attempt,
> ...
> ...
> 2014-11-14 17:45:37,258 INFO
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher: Launching
> masterappattempt_1412150883650_0001_000002
> ...
> ...
> The application attempt has the ID format "_1412150883650_0001_000002".
> Whereas the associated ContainerID goes by "_1412150883650_0001_02_".
> ...
> ...
> 2014-11-14 17:45:37,260 INFO
> org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher: Setting
> up
> container Container: [ContainerId: container_1412150883650_0001_02_000001,
> NodeId: n67:55933, NodeHttpAddress: n67:8042, Resource: <memory:2048,
> vCores:1,
> disks:0.0>, Priority: 0, Token: Token { kind: ContainerToken, service:
> 10.10.70.67:55933 }, ] for AM appattempt_1412150883650_0001_000002
> ...
> ...
> Curious to know if this is kept like that for a reason. If not while using
> filtering tools to, say, grep events surrounding a specific attempt by the
> numeric ID part information may slip out during troubleshooting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
