[
https://issues.apache.org/jira/browse/YARN-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated YARN-6977:
------------------------------
Fix Version/s: 2.10.2
I've cherry-picked this back to branch-2.10
> 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
> Priority: Major
> Labels: newbie
> Fix For: 3.0.0-beta1, 2.10.2
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
