diff options
| author | Nick Mills-Barrett <nick@beeper.com> | 2022-04-01 14:33:25 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-01 13:33:25 +0000 |
| commit | 993d90f82ba8faace30cbdaace5a8c5a4468b32a (patch) | |
| tree | 45fe1f79f1b917675c94d517d141922b17e36a46 /docs | |
| parent | Remove `list_url_patterns` dev script (#12349) (diff) | |
| download | synapse-993d90f82ba8faace30cbdaace5a8c5a4468b32a.tar.xz | |
Use a sequence to generate AS transaction IDs, drop `last_txn` AS state (#12209)
Switching to a sequence means there's no need to track `last_txn` on the AS state table to generate new TXN IDs. This also means that there is no longer contention between the AS scheduler and AS handler on updates to the `application_services_state` table, which will prevent serialization errors during the complete AS txn transaction.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/upgrade.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/upgrade.md b/docs/upgrade.md index 062e823333..f6d226526a 100644 --- a/docs/upgrade.md +++ b/docs/upgrade.md @@ -85,6 +85,19 @@ process, for example: dpkg -i matrix-synapse-py3_1.3.0+stretch1_amd64.deb ``` +# Upgrading to v1.57.0 + +## Changes to database schema for application services + +Synapse v1.57.0 includes a [change](https://github.com/matrix-org/synapse/pull/12209) to the +way transaction IDs are managed for application services. If your deployment uses a dedicated +worker for application service traffic, **it must be stopped** when the database is upgraded +(which normally happens when the main process is upgraded), to ensure the change is made safely +without any risk of reusing transaction IDs. + +Deployments which do not use separate worker processes can be upgraded as normal. Similarly, +deployments where no applciation services are in use can be upgraded as normal. + # Upgrading to v1.56.0 ## Groups/communities feature has been deprecated |