You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2014/04/02 05:15:16 UTC

[jira] [Updated] (YARN-1892) Excessive logging in RM

     [ https://issues.apache.org/jira/browse/YARN-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jian He updated YARN-1892:
--------------------------

    Attachment: YARN-1892.2.patch

Added a side fix to move "sending container statuses... " in NodeStatusUpdater to info level

> Excessive logging in RM
> -----------------------
>
>                 Key: YARN-1892
>                 URL: https://issues.apache.org/jira/browse/YARN-1892
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Siddharth Seth
>            Assignee: Jian He
>            Priority: Minor
>         Attachments: YARN-1892.1.patch, YARN-1892.2.patch
>
>
> Mostly in the CS I believe
> {code}
>  INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt: Application application_1395435468498_0011 reserved container container_1395435468498_0011_01_000213 on node host:  #containers=5 available=4096 used=20960, currently has 1 at priority 4; currentReservation 4096
> {code}
> {code}
> INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: hive2 usedResources: <memory:20480, vCores:5> clusterResources: <memory:81920, vCores:16> currentCapacity 0.25 required <memory:4096, vCores:1> potentialNewCapacity: 0.255 (  max-capacity: 0.25)
> {code}



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