Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-4854

Capacity Scheduler should read the reclaim-capacity-interval config value from its own config file

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 0.20.0
    • None
    • None
    • Reviewed

    Description

      The Capacity Scheduler needs to know the time interval for checking whether capacity needs to be reclaimed. This is represented by the static variable RECLAIM_CAPACITY_INTERVAL. This value is currently read as follows:

          RECLAIM_CAPACITY_INTERVAL = conf.getLong("mapred.capacity-scheduler.reclaimCapacity.interval", 5);
      

      This is incorrect for the following reasons:

      • ""mapred.capacity-scheduler.reclaimCapacity.interval" is not present in any of the config files: hadoop-site.xml or capacity-scheduler.xml.
      • "mapred.capacity-scheduler.reclaimCapacity.interval" should be specified in the scheduler's config file, capacity-scheduler.xml. It should be read through org.apache.hadoop.mapred.CapacitySchedulerConf.
      • The Forrest documentation for the Capacity Scheduler should describe this setting. We should probably create a new sub-section under 'Configuration', titled 'Configuring properties for the Scheduler'.

      Attachments

        1. HADOOP-4854-1.patch
          6 kB
          Sreekanth Ramakrishnan
        2. HADOOP-4854-2.patch
          6 kB
          Sreekanth Ramakrishnan
        3. HADOOP-4854-3.patch
          8 kB
          Sreekanth Ramakrishnan
        4. HADOOP-4854-4.patch
          8 kB
          Sreekanth Ramakrishnan
        5. HADOOP-4854-5.patch
          8 kB
          Sreekanth Ramakrishnan

        Activity

          People

            sreekanth Sreekanth Ramakrishnan
            vivekr Vivek Ratan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: