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
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ HDFS currently requires a manual process to upgrade. This guide will take you th
6
6
7
7
== Preparing HDFS
8
8
9
-
HDFS must be configured to initiate the upgrade process. To do this, run the following commands in an HDFS superuser environment
9
+
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
10
10
(either a client configured with a superuser account, or from inside a NameNode pod):
11
11
12
12
// This could be automated by the operator, but dfsadmin does not have good machine-readable output.
Then wait until all pods have restarted, are in the Ready state, and running the new HDFS version.
56
56
57
+
NOTE: This will automatically enable the NameNodes' compatibility mode, allowing them to start despite the fsImage version mismatch.
58
+
57
59
NOTE: Services will be upgraded in order: JournalNodes, then NameNodes, then DataNodes.
58
60
59
61
== Finalizing the upgrade
@@ -72,14 +74,14 @@ Rolling upgrade is finalized.
72
74
73
75
// We can't safely automate this, because finalize is asynchronous and doesn't tell us whether all NameNodes have even received the request to finalize.
74
76
75
-
WARNING: Please ensure that all NameNodes are running and available before proceeding. NameNodes that have not finalized yet will crash on launch when taken out of upgrade mode.
77
+
WARNING: Please ensure that all NameNodes are running and available before proceeding. NameNodes that have not finalized yet will crash on launch when taken out of compatibility mode.
76
78
77
-
Finally, the operator and cluster should be taken out of upgrade mode, by marking the HdfsCluster as upgraded to the new version:
0 commit comments