devmadhuu opened a new pull request, #10815:
URL: https://github.com/apache/ozone/pull/10815

   ## What changes were proposed in this pull request?
   Thread a `StorageTier` from the SCM block-allocation RPC down to 
`PipelineFactory.create`, so callers can request a pipeline (and, via  #10810 , 
a container) on a specific storage tier. Removes the  `// TODO StoragePolicy 
replace this StorageTier with the passed  StorageTier` hardcode in 
`PipelineFactory` that forced every  pipeline creation onto DISK.  
   
   Please describe your PR in detail:
   1. Thread StorageTier through the block-allocation RPC and BlockManager
   2. Wire StorageTier into PipelineManager and PipelineFactory 
   
   Depends on #10810  (which adds a persisted `StorageTier` field to  
`ContainerInfo`)
   
   Now with this PR:
    - OM can now send a tier on `AllocateScmBlock`.                             
                                                                                
                                             
     - SCM builds a pipeline on that tier (via 
`RatisPipelineProvider`/`ECPipelineProvider`, already tier-capable  from 
HDDS-15250).                                                                    
                                                                                
                                  
     - The allocated container inherits the tier from its pipeline (via  
#10810) and survives SCM restart.
   
   ## What is the link to the Apache JIRA
   https://issues.apache.org/jira/browse/HDDS-15249
   
   ## How was this patch tested?
   Updated and extended tests in `TestBlockManager`, 
`TestSCMBlockProtocolServer`
   


-- 
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]

Reply via email to