[YARN-2159] Better logging in SchedulerNode#allocateContainer

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 2.5.0
• Component/s: resourcemanager
• Labels: newbie supportability
• Target Version/s: 2.5.0
• Hadoop Flags: Reviewed
• Assignee: Ray Chiang
• Reporter: Ray Chiang
• Created: 13/Jun/14 20:28
• Updated: 15/Aug/14 05:44
• Resolved: 16/Jun/14 22:19

Description

This bit of code:

LOG.info("Assigned container " + container.getId() + " of capacity "
+ container.getResource() + " on host " + rmNode.getNodeAddress()
+ ", which currently has " + numContainers + " containers, "
+ getUsedResource() + " used and " + getAvailableResource()
+ " available");

results in a line like:

2014-05-30 16:17:43,573 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode: Assigned container container_1400666605555_0009_01_001111 of capacity <memory:1536, vCores:1> on host machine.host.domain.com:8041, which currently has 18 containers, <memory:27648, vCores:18> used and <memory:3072, vCores:0> available

That message is fine in most cases, but looks pretty bad after the last available allocation, since it says something like "vCores:0 available".

Here is one suggested phrasing

• "which has 18 containers, <memory:27648, vCores:18> used and <memory:3072, vCores:0> available after allocation"