Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-10997

Revisit allocation and reservation logging

    XMLWordPrintableJSON

Details

    • Reviewed

    Description

      Accepted allocation proposal and reserved container logs are two exceedingly frequent events. Numerous user reported that these log entries had quickly filled the logs on a busy cluster and seen these entries only as noise.

      It would be worthwhile to reduce the log level of these entries to DEBUG level.

      Examples:

      2021-10-30 02:28:57,409 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Allocation proposal accepted
      2021-10-30 02:28:57,439 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.common.fica.FiCaSchedulerApp: Reserved container=container_1635478503131_0069_01_000078, on node=host: node:8041 #containers=1 available=<memory:1835, vCores:3> used=<memory:3072, vCores:1> with resource=<memory:3072, vCores:1>
      

      Attachments

        Issue Links

          Activity

            People

              gandras Andras Gyori
              gandras Andras Gyori
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h 20m
                  1h 20m