[ 
https://issues.apache.org/jira/browse/HDDS-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554280#comment-17554280
 ] 

Ethan Rose edited comment on HDDS-6885 at 6/14/22 8:30 PM:
-----------------------------------------------------------

To finalize HDDS-6360 (one rocksDB per volume) without closing containers, 
HDDS-6887 will need to be implemented.


was (Author: erose):
To finalize HDDS-6360 (one rocksDB per volume) without closing containers, 
HDDS-6886 will need to be implemented.

> Allow HDDS layout features to specify their finalization requirements
> ---------------------------------------------------------------------
>
>                 Key: HDDS-6885
>                 URL: https://issues.apache.org/jira/browse/HDDS-6885
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Datanode, SCM
>            Reporter: Ethan Rose
>            Assignee: Ethan Rose
>            Priority: Major
>
> Add a field to each HDDS layout feature object that allows it to specify the 
> requirements SCM must enforce when it needs to be finalized. Currently there 
> will be two options:
> 1. Close all containers: The current way finalization works, which involves 
> closing all pipelines and containers and moving datanodes to a readonly state 
> until they finalize.
> 2. None: No special requirements. The layout feature can be finalized while 
> datanodes are serving reads and writes. Individual datanodes must still be 
> finalized before they can use new layout features.
> Another requirement could be the number of datanodes that must finalize 
> before SCM declares finalization as complete. A minimum number may be 
> configured by default, but some features like erasure coding may have a 
> specific number, like 5, needed before the feature can be declared finalized. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Reply via email to