Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-3816 Erasure Coding
  3. HDDS-5327

EC: WritableEcContainerProvider should dynamically adjust the open container groups

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: SCM
    • Labels:
      None

      Description

      After some discussion we concluded that for any given EC policy, a minimum number of pipelines should be allocated so writes can be directed to different containers.

      The absolute maximum number of pipelines can be calculated as some function of the cluster nodes and disks, but we are still unsure about how to calculate that limit.

      The number of pipelines should be able to grow from the minimum toward the maximum, depending on the write load on the cluster, or perhaps the age of the oldest open container (to prevent too many containers remaining open for too long).

      The goal is to allow a sufficient number of open containers so the writes are spread across different disks, without having to maintain too many open containers on the cluster.

      If the write load is very high, there should be more open containers than if the write load is very low.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              sodonnell Stephen O'Donnell
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: