hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2159) Better logging in SchedulerNode#allocateContainer
Date Tue, 17 Jun 2014 11:28:04 GMT

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

Hudson commented on YARN-2159:
------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #586 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/586/])
YARN-2159. Better logging in SchedulerNode#allocateContainer. (Ray Chiang via kasha) (kasha:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1603003)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerNode.java


> Better logging in SchedulerNode#allocateContainer
> -------------------------------------------------
>
>                 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: Trivial
>              Labels: newbie, supportability
>             Fix For: 2.5.0
>
>         Attachments: YARN2159-01.patch
>
>
> This bit of code:
> {quote}
>     LOG.info("Assigned container " + container.getId() + " of capacity "
>         + container.getResource() + " on host " + rmNode.getNodeAddress()
>         + ", which currently has " + numContainers + " containers, "
>         + getUsedResource() + " used and " + getAvailableResource()
>         + " available");
> {quote}
> results in a line like:
> {quote}
> 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
> {quote}
> 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"



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

Mime
View raw message