Skip to content

Commit f0df2b7

Browse files
committed
Upgrade mode -> compatibility mode
1 parent d5a092a commit f0df2b7

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/modules/hdfs/pages/usage-guide/upgrading.adoc

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ HDFS currently requires a manual process to upgrade. This guide will take you th
66

77
== Preparing HDFS
88

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
1010
(either a client configured with a superuser account, or from inside a NameNode pod):
1111

1212
// This could be automated by the operator, but dfsadmin does not have good machine-readable output.
@@ -54,6 +54,8 @@ hdfscluster.hdfs.stackable.tech/simple-hdfs patched
5454

5555
Then wait until all pods have restarted, are in the Ready state, and running the new HDFS version.
5656

57+
NOTE: This will automatically enable the NameNodes' compatibility mode, allowing them to start despite the fsImage version mismatch.
58+
5759
NOTE: Services will be upgraded in order: JournalNodes, then NameNodes, then DataNodes.
5860

5961
== Finalizing the upgrade
@@ -72,14 +74,14 @@ Rolling upgrade is finalized.
7274

7375
// 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.
7476

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.
7678

77-
Finally, the operator and cluster should be taken out of upgrade mode, by marking the HdfsCluster as upgraded to the new version:
79+
Finally, we mark the cluster as upgraded:
7880

7981
[source,shell]
8082
----
8183
$ kubectl patch hdfs/simple-hdfs --subresource=status --patch '{"status": {"deployedProductVersion": "3.4.0"}}' --type=merge
8284
hdfscluster.hdfs.stackable.tech/simple-hdfs patched
8385
----
8486

85-
NOTE: The NameNodes will be restarted a final time, taking them out of upgrade mode.
87+
NOTE: The NameNodes will be restarted a final time, taking them out of compatibility mode.

0 commit comments

Comments
 (0)