Skip to content

Commit

Permalink
[docs] Explain downgrades aren't supported. (#13678)
Browse files Browse the repository at this point in the history
Co-authored-by: Alex Ball <aball@yugabyte.com>
  • Loading branch information
ddorian and Alex Ball authored Aug 19, 2022
1 parent 86a78b7 commit 5dcd9c6
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/content/preview/manage/upgrade-deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,9 @@ $ ./bin/yb-admin -timeout_ms 180000 upgrade_ysql
Upgrading the YSQL system catalog is an online operation and doesn't require stopping a running cluster. `upgrade_ysql` is idempotent and can be run multiple times without any side effects.

{{< note title="Note" >}}
{{< note title="Notes" >}}
Concurrent operations in a cluster can lead to various transactional conflicts, catalog version mismatches, and read restart errors. This is expected, and should be addressed by re-running `upgrade_ysql`.

Downgrades aren't currently supported. This is tracked in GitHub issue [#13686](https://github.com/yugabyte/yugabyte-db/issues/13686).
{{< /note >}}

0 comments on commit 5dcd9c6

Please sign in to comment.