forked from TrueCloudLab/frostfs-node
[#83] pre-commit: Add initial configuration
Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
This commit is contained in:
parent
24a540caa8
commit
861e9ab59a
31 changed files with 163 additions and 146 deletions
|
@ -4,7 +4,7 @@
|
|||
|
||||
Each mode is characterized by two important properties:
|
||||
1. Whether modifying operations are allowed.
|
||||
2. Whether metabase and write-cache is available.
|
||||
2. Whether metabase and write-cache is available.
|
||||
The expected deployment scenario is to place both metabase and write-cache on an SSD drive thus these modes
|
||||
can be approximately described as no-SSD modes.
|
||||
|
||||
|
@ -45,4 +45,4 @@ However, all mode changing operations are idempotent.
|
|||
Shard can automatically switch to a `degraded-read-only` mode in 3 cases:
|
||||
1. If the metabase was not available or couldn't be opened/initialized during shard startup.
|
||||
2. If shard error counter exceeds threshold.
|
||||
3. If the metabase couldn't be reopened during SIGHUP handling.
|
||||
3. If the metabase couldn't be reopened during SIGHUP handling.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue