Devesh Kumar Singh created HDDS-17712:
-----------------------------------------

             Summary: Preserve container tier intent during fallback and 
automatically restore preferred placement
                 Key: HDDS-17712
                 URL: https://issues.apache.org/jira/browse/HDDS-17712
             Project: Apache Ozone
          Issue Type: Sub-task
          Components: Ozone Client, Ozone Datanode
            Reporter: Devesh Kumar Singh
            Assignee: Devesh Kumar Singh


A HOT key can have Block 1 allocated on SSD and Block 2 allocated on DISK 
through permitted creation fallback. Currently, SCM records the fallback 
container's tier as DISK. The key retains its HOT policy in OM, but SCM has no 
implemented automatic promotion workflow that moves the fallback data to SSD 
when suitable SSD capacity becomes available. The container, replica metadata, 
and volume can all report DISK, so ordinary container consistency checks do not 
identify the outstanding HOT placement requirement.

Preserve the intended SSD tier in SCM container metadata and the replica's 
storage-type metadata while allowing an explicitly authorized initial placement 
on DISK. Keep the actual volume type in the existing separate volume report. 
Use a normal DISK pipeline for fallback; no special pipeline type, special 
container type, or additional "dedicated container" flag is required. Container 
selection must distinguish the desired tier so ordinary WARM/DISK containers 
are not relabelled or mixed into this promotion workflow.

Carry the intended type, selected placement, and fallback authorization 
consistently through allocation, client requests, datanode creation/import, 
reporting, and capacity accounting. Add RM assessment and a bounded background 
movement workflow that retains valid DISK replicas while SSD is unavailable and 
promotes them safely when suitable SSD capacity becomes available. Preserve 
replica metadata as SSD before and after promotion; only the actual volume 
changes. Include restart, partial failure, compatibility, and end-to-end tests.





--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to