Details

    • Type: Sub-task
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.5.1
    • Fix Version/s: None
    • Component/s: scheduler
    • Labels:
      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

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated: