[
https://issues.apache.org/jira/browse/HDDS-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712392#comment-17712392
]
Vyacheslav Tutrinov commented on HDDS-1575:
-------------------------------------------
Anyone who will work on the ticket, please try to investigate/implement a way
to support the feature as a pluggable or configurable one. Now we actively work
on the write-cache feature and would like to have the option to deal with
SCM/DN in a previous manner (without changed and hard-coded behavior of the
logic to select blocks location). Would be great to have an interface like
'BlockLocationSelector' and to have the current implementation as a default one
and a new 'StoragePolicyBasedBlocksLocationSelector' impl could be set as
preferable one by setting the 'ozone.block.location.selector' configuration
property.
> 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]
