hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MUFEED USMAN (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3017) ContainerID in ResourceManager Log Has Slightly Different Format From AppAttemptID
Date Sat, 10 Jan 2015 04:53:34 GMT

    [ https://issues.apache.org/jira/browse/YARN-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272339#comment-14272339
] 

MUFEED USMAN commented on YARN-3017:
------------------------------------

This is what I have,

{code}
[root@n67 ~]# yarn version
Hadoop 2.4.1-mapr-1408
Subversion git@github.com:mapr/private-hadoop-common -r 8adc7b2bf05973f6bd0783f0ae11018c4e374ec6
Compiled by root on 2014-09-05T16:33Z
Compiled with protoc 2.5.0
>From source with checksum d6a27c2cce7dfc75f2466d7da7ef7c
This command was run using /opt/mapr/hadoop/hadoop-2.4.1/share/hadoop/common/hadoop-common-2.4.1-mapr-1408.jar
{code}

> 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)

Mime
View raw message