forked from TrueCloudLab/frostfs-node
[#1745] neofs-node: Remove memcache_capacity
from the configuration
It is unused since ddaed283e9
.
Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
This commit is contained in:
parent
bda084f331
commit
177e8e01b1
11 changed files with 5 additions and 45 deletions
|
@ -252,7 +252,6 @@ writecache:
|
|||
enabled: true
|
||||
path: /path/to/writecache
|
||||
capacity: 4294967296
|
||||
memcache_capacity: 2147483648
|
||||
small_object_size: 16384
|
||||
max_object_size: 134217728
|
||||
workers_number: 30
|
||||
|
@ -262,7 +261,6 @@ writecache:
|
|||
|----------------------|------------|---------------|----------------------------------------------------------------------------------------------------------------------|
|
||||
| `path` | `string` | | Path to the metabase file. |
|
||||
| `capacity` | `size` | unrestricted | Approximate maximum size of the writecache. If the writecache is full, objects are written to the blobstor directly. |
|
||||
| `memcache_capacity` | `size` | `1G` | Maximum size of the memory-cache. |
|
||||
| `small_object_size` | `size` | `32K` | Maximum object size for "small" objects. This objects are stored in a key-value database instead of a file-system. |
|
||||
| `max_object_size` | `size` | `64M` | Maximum object size allowed to be stored in the writecache. |
|
||||
| `workers_number` | `int` | `20` | Amount of background workers that move data from the writecache to the blobstor. |
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue