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

      The Pipeline level storage policy can be thought of segregating write bandwidth for high throughput writes or random reads use cases when SSDs, NVMe or RAM disks are involved by not having to figure out write pipelines on the fly. The Datanode would need to read the pipeline policy and route write to appropriate storage volumes. An Ozone mover can be provided for the archival data use case.

      Additionally, it makes sense to permeate the policy information to Containers, this will help when allocateBlock call for a key with storage policy set to ALL_SSD, to be routed to an open container on a Pipeline with the same policy setting. The caveat is that at least one open pipeline needs to be maintained at all times in order to support storage the policy setting.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              swagle Siddharth Wagle
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: