greenwich commented on PR #10380:
URL: https://github.com/apache/ozone/pull/10380#issuecomment-4581714671
> By the way, have you guys tried using the Storage Policy feature
internally yet?
On trying it internally: not end-to-end yet. The merged work plus this PR
gives a solid datanode foundation (select/persist/create container by
StorageType) and SCM replica-tier visibility, but the write path that would use
it isn't wired on HDDS-11233 yet — OM doesn't read a bucket/key policy at
allocation, the block location carries no storage type, and SCM
allocation/pipelines aren't tier-aware. So two buckets tagged for different
tiers still land on the same hardware today.
We're excited about the feature and are following closely. Once the
placement path is finalised, we'd be happy to validate it on a mixed SSD/HDD
cluster or provide any other help if needed. Is that roughly the next milestone
you're targeting?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
