You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2022/10/25 00:08:00 UTC

[jira] [Resolved] (HDDS-5474) Stop reads and writes on datanodes during major upgrades

     [ 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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org