[
https://issues.apache.org/jira/browse/HDDS-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose resolved HDDS-5474.
------------------------------
Resolution: Won't Fix
Current discussions and use cases around upgrade finalization are leaning more
towards it remaining as a sort of feature flag off-to-on switch that is
lightweight and unobtrusive while the cluster is running. For this reason we
will probably not be implementing this feature.
> Stop reads and writes on datanodes during major upgrades
> --------------------------------------------------------
>
> Key: HDDS-5474
> URL: https://issues.apache.org/jira/browse/HDDS-5474
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Priority: Major
>
> Some backwards incompatible changes like HDDS-4866 may need to reformat
> containers or volumes during upgrade. We currently cannot safely do this
> during finalize because we do not block reads on the datanode while it is
> finalizing, only writes. This jira is to investigate having an option to
> block writes on datanodes during finalization of more invasive upgrade
> actions, while leaving the normal read only requirement for minor upgrade
> changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
