[HDDS-5444] Ozone Upgrades vNext

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Ethan Rose
• Reporter: Aravindan Vijayan
• Created: 14/Jul/21 21:12
• Updated: 23/Mar/23 18:31

Description

Tracking epic for spillover items from v1 non-rolling upgrades story. Scope will be defined here in a few weeks.

Issue Links

• is a parent of: HDDS-5141 Add support for finalizing an SCM HA based cluster
• is a parent of: HDDS-6884 Allow writes while finalizing non-invasive layout features.
• is a parent of: HDDS-8264 SCM HA Finalization v2

Sub-Tasks

• On finalize upgrade actions not running: Resolved
• Race condition upon dn restart at prefinalization: Resolved
• Skip check for UNHEALTHY containers for datanode finalize.: Resolved
• SKip update firstUpgradeActionLayoutVersion when on-disk layout version is up-to-date: Resolved
• Duplicate metrics registered while running checkScmHA upon scm startup: Resolved
• Containers are always quasi closed during finalization: Resolved
• Enable downgrade testing after 1.1.0 release: Resolved
• Publish upgrade documentation on Ozone website: Resolved
• Pluggable OzoneManager request handling hooks: Resolved
• General Purpose Client Versioning: Resolved
• Ensure LayoutVersion is unique and monotonicaly increasing in LayoutFeature enums: Resolved
• Datanodes' dnlayoutversion/VERSION file contains incorrect cluster ID: Resolved
• Stop reads and writes on datanodes during major upgrades: Resolved
• Investigate using existing volume layout versions: Resolved
• Auto-generate the XML for aspect weaver: Open
• Implement one-by-one LayoutFeature finalization in OMUpgradeFinalizer: Open
• Datanode snapshot can be installed while pre-finalize actions are running: Open
• New HEALTHY_READONLY state should be operational state instead of health state?: Open