MirrorHub/synapse
0
0
Fork 1
mirror of https://mau.dev/maunium/synapse.git synced 2024-12-15 03:23:54 +01:00
Code Issues Projects Releases Wiki Activity

Update documentation on retention policies limits (#8529)

Browse source 
* Update documentation on retention policies limits

Document the changes from https://github.com/matrix-org/synapse/pull/8104
This commit is contained in:
Brendan Abolivier 2020-10-14 15:00:49 +01:00 committed by GitHub
parent 1264c8ac89
commit 9e66f3761c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 23 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelog.d/8529.doc Normal file
View file

@ -0,0 +1 @@
Document the new behaviour of the `allowed_lifetime_min` and `allowed_lifetime_max` settings in the room retention configuration.

34
docs/message_retention_policies.md
View file

@ -136,24 +136,34 @@ the server's database.
### Lifetime limits ### Lifetime limits
**Note: this feature is mainly useful within a closed federation or on Server admins can set limits on the values of `max_lifetime` to use when
servers that don't federate, because there currently is no way to purging old events in a room. These limits can be defined as such in the
enforce these limits in an open federation.** `retention` section of the configuration file:
Server admins can restrict the values their local users are allowed to
use for both `min_lifetime` and `max_lifetime`. These limits can be
defined as such in the `retention` section of the configuration file:
```yaml ```yaml
allowed_lifetime_min: 1d allowed_lifetime_min: 1d
allowed_lifetime_max: 1y allowed_lifetime_max: 1y
``` ```
Here, `allowed_lifetime_min` is the lowest value a local user can set The limits are considered when running purge jobs. If necessary, the
for both `min_lifetime` and `max_lifetime`, and `allowed_lifetime_max` effective value of `max_lifetime` will be brought between
is the highest value. Both parameters are optional (e.g. setting `allowed_lifetime_min` and `allowed_lifetime_max` (inclusive).
`allowed_lifetime_min` but not `allowed_lifetime_max` only enforces a This means that, if the value of `max_lifetime` defined in the room's state
minimum and no maximum). is lower than `allowed_lifetime_min`, the value of `allowed_lifetime_min`
will be used instead. Likewise, if the value of `max_lifetime` is higher
than `allowed_lifetime_max`, the value of `allowed_lifetime_max` will be
used instead.
In the example above, we ensure Synapse never deletes events that are less
than one day old, and that it always deletes events that are over a year
old.
If a default policy is set, and its `max_lifetime` value is lower than
`allowed_lifetime_min` or higher than `allowed_lifetime_max`, the same
process applies.
Both parameters are optional; if one is omitted Synapse won't use it to
adjust the effective value of `max_lifetime`.
Like other settings in this section, these parameters can be expressed Like other settings in this section, these parameters can be expressed
either as a duration or as a number of milliseconds. either as a duration or as a number of milliseconds.