Mercurial > prosody-modules
view mod_storage_multi/README.markdown @ 4877:adc6241e5d16
mod_measure_process: Report the enforced limit
The soft limit is what the kernel actually enforces, while the hard
limit is is how far you can change the soft limit without privileges.
Unless the process dynamically adjusts the soft limit, knowing the hard
limit is not as useful as knowing the soft limit.
Reporting the soft limit and the number of in-use FDs allows placing
alerts on expressions like 'process_open_fds / process_max_fds >= 0.95'
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 18 Jan 2022 18:55:20 +0100 |
parents | a7fdab9c14e2 |
children |
line wrap: on
line source
--- summary: Multi-backend storage module (WIP) labels: - NeedDocs - Stage-Alpha ... Introduction ============ This module attemtps to provide a storage driver that is really multiple storage drivers. This could be used for storage error tolerance or caching of data in a faster storage driver. Configuration ============= An example: ``` {.lua} storage = "multi" storage_multi_policy = "all" storage_multi = { "memory", "internal", "sql" } ``` Here data would be first read from or written to [mod\_storage\_memory], then internal storage, then SQL storage. For reads, the first successful read will be used. For writes, it depends on the `storage_multi_policy` option. If set to `"all"`, then all storage backends must report success for the write to be considered successful. Other options are `"one"` and `"majority"`.