[
https://issues.apache.org/jira/browse/HDDS-6886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554277#comment-17554277
]
Ethan Rose commented on HDDS-6886:
----------------------------------
Some ideas to get started:
1. Rename the HEALTHY_READONLY state to something specific to finalization.
2. Use the {{DatanodeInfo#lastKnownLayoutVersion}} field to make finalization
based decisions instead of the datanode state.
> No longer use HEALTHY_READONLY state to indicate pre-finalized datanodes
> ------------------------------------------------------------------------
>
> Key: HDDS-6886
> URL: https://issues.apache.org/jira/browse/HDDS-6886
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Priority: Minor
>
> The upgrade framework introduced the HEALTHY_READONLY state, which datanodes
> are moved to when their metadata layout version is behind SCM's. With the
> option for finalization to not block write operations, a 1-to-1
> correspondence between this state and a datanode that needs finalization no
> loner makes sense.
> This Jira is an investigative task to figure out how to better handle this
> without major incompatible proto changes. In the mean time SCM can continue
> to use the state to refer to datanodes that need finalization without any
> correctness issues, but it may pose confusion for developers and users in the
> long term.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
