[ https://issues.apache.org/jira/browse/YARN-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168877#comment-16168877 ]
Hudson commented on YARN-6977: ------------------------------ SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12892 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/12892/]) YARN-6977. Node information is not provided for non am containers in RM (wangda: rev 958e8c0e257216c82f68fee726e5280a919da94a) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerNode.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSSchedulerNode.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerNode.java > Node information is not provided for non am containers in RM logs > ----------------------------------------------------------------- > > Key: YARN-6977 > URL: https://issues.apache.org/jira/browse/YARN-6977 > Project: Hadoop YARN > Issue Type: Bug > Components: capacity scheduler > Reporter: Sumana Sathish > Assignee: Suma Shivaprasad > Labels: newbie > Fix For: 3.0.0-beta1 > > Attachments: YARN-6977.002.patch, YARN-6977.patch > > > There is no information on which node non am container is being assigned in > the trunk for hadoop 3.0 > Earlier we used to have logs for non am container in the similar way > {code} > Assigned container container_ of capacity <memory:4096, vCores:1> on host > <host>, which has 1 containers, <memory:4096, vCores:1> used and > <memory:8192, vCores:0> available after allocation > {code} > 3.0 has information for am container alone in the following way > {code} > Done launching container Container: [ContainerId: container_, > AllocationRequestId: 0, Version: 0, NodeId:nodeID, NodeHttpAddress: > nodeAddress, Resource: <memory:11264, vCores:1>, Priority: 0, Token: Token { > kind: ContainerToken, service: service}, ExecutionType: GUARANTEED, ] for AM > appattempt_ > {code} > Can we please have similar message for Non am container too ?? -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org