Details

    • Sub-task
    • Status: Reopened
    • Major
    • Resolution: Unresolved
    • 2.5.1
    • None
    • scheduler
    • None

    Description

      Currently, the number of disks present on a node is not considered a factor while scheduling containers on that node. Having large amount of memory on a node can lead to high number of containers being launched on that node, all of which compete for I/O bandwidth. This multiplexing of I/O across containers can lead to slower overall progress and sub-optimal resource utilization as containers starved for I/O bandwidth hold on to other resources like cpu and memory. This problem can be solved by considering disk as a resource and including it in deciding how many containers can be concurrently run on a node.

      Attachments

        1. DiskDriveAsResourceInYARN.pdf
          502 kB
          Swapnil Daingade

        Issue Links

          Activity

            People

              yufeldman Yuliya Feldman
              sdaingade Swapnil Daingade
              Votes:
              2 Vote for this issue
              Watchers:
              35 Start watching this issue

              Dates

                Created:
                Updated: