aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAlex Auvolat <alex@adnab.me>2023-09-07 12:52:44 +0200
committerAlex Auvolat <alex@adnab.me>2023-09-07 12:52:44 +0200
commitbca347a1e8e4bb74e744ec8e020b8144c6cafdf3 (patch)
tree36a0ff1d96c721332b2ff322ee1e54d8bdefda13 /doc
parent99ed18350f9572ebb1968107d3708d53682ee805 (diff)
downloadgarage-bca347a1e8e4bb74e744ec8e020b8144c6cafdf3.tar.gz
garage-bca347a1e8e4bb74e744ec8e020b8144c6cafdf3.zip
doc: update page on upgradin clusters
Diffstat (limited to 'doc')
-rw-r--r--doc/book/operations/upgrading.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/book/operations/upgrading.md b/doc/book/operations/upgrading.md
index e8919a19..9a738282 100644
--- a/doc/book/operations/upgrading.md
+++ b/doc/book/operations/upgrading.md
@@ -80,6 +80,6 @@ The entire procedure would look something like this:
5. If any specific migration procedure is required, it is usually in one of the two cases:
- It can be run on online nodes after the new version has started, during regular cluster operation.
- - it has to be run offline
+ - it has to be run offline, in which case you will have to again take all nodes offline one after the other to run the repair
For this last step, please refer to the specific documentation pertaining to the version upgrade you are doing.