hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Chiang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-2159) allocateContainer() in SchedulerNode needs a clearer LOG.info message
Date Fri, 13 Jun 2014 20:29:02 GMT
Ray Chiang created YARN-2159:
--------------------------------

             Summary: allocateContainer() in SchedulerNode needs a clearer LOG.info message
                 Key: YARN-2159
                 URL: https://issues.apache.org/jira/browse/YARN-2159
             Project: Hadoop YARN
          Issue Type: Improvement
          Components: resourcemanager
            Reporter: Ray Chiang
            Assignee: Ray Chiang
            Priority: Minor


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".

Perhaps one of the following phrasings is better?

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



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message