From a189eca5d5e2285c78511a0a08acca5e19ff35c9 Mon Sep 17 00:00:00 2001 From: Evgenii Stratonikov Date: Sun, 16 Oct 2022 14:39:31 +0300 Subject: [PATCH] [#1908] docs: Describe SIGHUP behaviour Signed-off-by: Evgenii Stratonikov --- docs/sighup.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 docs/sighup.md diff --git a/docs/sighup.md b/docs/sighup.md new file mode 100644 index 0000000000..4243d620c1 --- /dev/null +++ b/docs/sighup.md @@ -0,0 +1,23 @@ +# SIGHUP behaviour + +## Logger + +Logger level can be reloaded with a SIGHUP. + +## Storage engine + +Shards can be added, removed or reloaded with SIGHUP. +Each shard from the configuration is matched with existing shards by +comparing paths from `shard.blobstor` section. After this we have 3 sets: + +1. Shards that are missing from the configuration (or have `mode: disabled`) but are currently open. + These are closed. +2. Shards that are added. These are opened and initialized. +3. Shards that remain in the configuration. + For these shards we apply reload to a `metabase` only. If `resync_metabase` is true, the metabase is also resynchronized. + +### Metabase + +| Changed section | Actions | +|-----------------|----------------------------------------------------------------------------------------------------------------------| +| `path` | If `path` is different, metabase is closed and opened with a new path. All other configuration will also be updated. |