carpawell/frostfs-node
1
0
Fork 0
forked from TrueCloudLab/frostfs-node
Code Issues Pull requests Projects Releases Packages Wiki Activity

[#1908] docs: Describe SIGHUP behaviour

Browse source 
Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
This commit is contained in:
Evgenii Stratonikov 2022-10-16 14:39:31 +03:00 committed by fyrchik
parent 1beafea0b5
commit a189eca5d5
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
docs/sighup.md Normal file
View file

@ -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. |