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

Capacity scheduler should initialize tasks asynchronously

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.19.0
    • Fix Version/s: 0.20.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Currently, the capacity scheduler initializes tasks on demand, as opposed to the eager initialization technique used by the default scheduler. This is done in order to save JT memory footprint. However, the initialization is done in the assignTasks API which is not a good idea as task initialization could be a time consuming operation. This JIRA is to move out the initialization outside the assignTasks API and do it asynchronously.

        Attachments

        1. HADOOP-4513-8.patch
          62 kB
          Hemanth Yamijala
        2. HADOOP-4513-6.patch
          58 kB
          Sreekanth Ramakrishnan
        3. HADOOP-4513-5-NOBUSYWAITING.patch
          58 kB
          Sreekanth Ramakrishnan
        4. HADOOP-4513-4.patch
          49 kB
          Sreekanth Ramakrishnan
        5. HADOOP-4513-3.patch
          49 kB
          Sreekanth Ramakrishnan
        6. HADOOP-4513-2.patch
          43 kB
          Sreekanth Ramakrishnan
        7. HADOOP-4513-1.patch
          42 kB
          Sreekanth Ramakrishnan

          Activity

            People

            • Assignee:
              sreekanth Sreekanth Ramakrishnan
              Reporter:
              yhemanth Hemanth Yamijala
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: