You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/modules/hdfs/pages/usage-guide/upgrading.adoc
+20Lines changed: 20 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,25 @@ IMPORTANT: HDFS upgrades are experimental, and details may change at any time
4
4
5
5
HDFS currently requires a manual process to upgrade. This guide will take you through an example case, upgrading an example cluster (from our xref:getting_started/index.adoc[Getting Started] guide) from HDFS 3.3.6 to 3.4.0.
6
6
7
+
== Preparing for the worst
8
+
9
+
Upgrades can fail, and it is important to prepare for when that happens. Apache HDFS supports https://hadoop.apache.org/docs/r3.4.0/hadoop-project-dist/hadoop-hdfs/HdfsRollingUpgrade.html#Downgrade_and_Rollback[two ways to revert an upgrade]:
10
+
11
+
Rollback:: Reverts all user data to the pre-upgrade state. Requires taking the cluster offline.
12
+
Downgrade:: Downgrades the HDFS software but preserves all changes made by users. Can be performed as a rolling change, keeping the cluster online.
13
+
14
+
The Stackable Operator for HDFS supports downgrading but not rollbacks.
15
+
16
+
In order to downgrade, revert the `.spec.image.productVersion` field, and then proceed to xref:#finalize[finalizing] once the cluster is downgraded:
WARNING: The Stackable Operator for HDFS will _not_ currently roll downgrades in order, they will incur some downtime.
25
+
7
26
== Preparing HDFS
8
27
9
28
HDFS must be configured to initiate the upgrade process. To do this, put the cluster into upgrade mode by running the following commands in an HDFS superuser environment
@@ -58,6 +77,7 @@ NOTE: This will automatically enable the NameNodes' compatibility mode, allowing
58
77
59
78
NOTE: Services will be upgraded in order: JournalNodes, then NameNodes, then DataNodes.
60
79
80
+
[#finalize]
61
81
== Finalizing the upgrade
62
82
63
83
Once all HDFS pods are running the new version, the HDFS upgrade can be finalized (from the HDFS superuser environment as described in the preparation step):
0 commit comments