Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify possible instances of zeebe rollback #4064

Merged
merged 2 commits into from
Jul 30, 2024
Merged

clarify possible instances of zeebe rollback #4064

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
851c92d
clarify possible instances of zeebe rollback
christinaausley Jul 25, 2024
387ef7c
resolve comments
christinaausley Jul 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/self-managed/zeebe-deployment/operations/update-zeebe.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,8 +160,12 @@ Because the update is no longer rolling and all brokers are shut down at the sam
If updated brokers log the error message `Failed to install partition` and do not become healthy, look for more details to understand if this is caused by the rolling update.

If the error is caused by `Cannot upgrade to or from a pre-release version`, Zeebe detected that either the version you started from or the version you updated to is a pre-release version.

This is not permitted because pre-release versions such as alpha releases are considered unstable and do not guarantee compatibility with any other version.
If you attempted to update from a normal version to a pre-release version, you can roll back to the previous normal version.

:::note
If you attempted to update from a minor release to a pre-release or alpha version, it is possible to roll back to the previous version of Zeebe. Note that version rollbacks are not supported in most other instances.
:::

If the log message includes `Snapshot is not compatible with current version`, the rolling update failed and manual recovery is required.

Expand Down Expand Up @@ -192,7 +196,7 @@ In that case, it is caused by updated brokers sharing snapshots with not yet upd
This should resolve automatically once the broker is updated.
:::

If this persists, you may want to [force the update](#rolling-update-is-not-completing).
If this persists, you can [force the update](#rolling-update-is-not-completing). Alternatively, it is possible to restart Zeebe with the "skipped" minor version. Note that version rollbacks are not supported in most other instances.

## Offline update

Expand Down
8 changes: 6 additions & 2 deletions ...ioned_docs/version-8.5/self-managed/zeebe-deployment/operations/update-zeebe.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,8 +160,12 @@ Because the update is no longer rolling and all brokers are shut down at the sam
If updated brokers log the error message `Failed to install partition` and do not become healthy, look for more details to understand if this is caused by the rolling update.

If the error is caused by `Cannot upgrade to or from a pre-release version`, Zeebe detected that either the version you started from or the version you updated to is a pre-release version.

This is not permitted because pre-release versions such as alpha releases are considered unstable and do not guarantee compatibility with any other version.
If you attempted to update from a normal version to a pre-release version, you can roll back to the previous normal version.

:::note
If you attempted to update from a minor release to a pre-release or alpha version, it is possible to roll back to the previous version of Zeebe. Note that version rollbacks are not supported in most other instances.
:::

If the log message includes `Snapshot is not compatible with current version`, the rolling update failed and manual recovery is required.

Expand Down Expand Up @@ -192,7 +196,7 @@ In that case, it is caused by updated brokers sharing snapshots with not yet upd
This should resolve automatically once the broker is updated.
:::

If this persists, you may want to [force the update](#rolling-update-is-not-completing).
If this persists, you can [force the update](#rolling-update-is-not-completing). Alternatively, it is possible to restart Zeebe with the "skipped" minor version. Note that version rollbacks are not supported in most other instances.

## Offline update

Expand Down
Loading