[
https://issues.apache.org/jira/browse/HDDS-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650633#comment-17650633
]
mingchao zhao commented on HDDS-1575:
-------------------------------------
Ozone 1.3.0 had been released and we currently have more than 600 open issues
targeted for 1.3.0. I am moving the target field to 1.4.0.
If there is anything needs to be discussed about the Target Version, Please
reach out to me via Apache email or Slack.
> Add support for storage policies to Pipelines
> ---------------------------------------------
>
> Key: HDDS-1575
> URL: https://issues.apache.org/jira/browse/HDDS-1575
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Reporter: Siddharth Wagle
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
