8b68830201
* Configure the file metadata cache for storage-users * Also configure the cache for the system storage * Update services/storage-system/pkg/config/config.go Co-authored-by: Martin <github@diemattels.at> * Improve documentation * Bump reva to pull in the latest ini backend changes * Fix missing comment * Update services/storage-users/README.md Co-authored-by: Martin <github@diemattels.at> * Update services/storage-system/README.md Co-authored-by: Martin <github@diemattels.at> * Tweak docs * Apply suggestions from code review Co-authored-by: Jörn Friedrich Dreyer <jfd@butonic.de> Co-authored-by: Martin <github@diemattels.at> --------- Co-authored-by: Martin <github@diemattels.at> Co-authored-by: Jörn Friedrich Dreyer <jfd@butonic.de>
18 lines
1.4 KiB
Markdown
18 lines
1.4 KiB
Markdown
# Storage-System Service
|
|
|
|
Purpose and description to be added
|
|
|
|
## Caching
|
|
|
|
The `storage-system` service caches file metadata via the configured store in `STORAGE_SYSTEM_CACHE_STORE`. Possible stores are:
|
|
- `memory`: Basic in-memory store and the default.
|
|
- `redis`: Stores metadata in a configured Redis cluster.
|
|
- `redis-sentinel`: Stores metadata in a configured Redis Sentinel cluster.
|
|
- `etcd`: Stores metadata in a configured etcd cluster.
|
|
- `nats-js`: Stores metadata using the key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
|
|
- `noop`: Stores nothing. Useful for testing. Not recommended in productive enviroments.
|
|
|
|
1. Note that in-memory stores are by nature not reboot persistent.
|
|
2. Though usually not necessary, a database name can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`, `redis` and `redis-sentinel`. These settings are blank by default which means that the standard settings of the configured store applies.
|
|
3. The `storage-system` service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances.
|
|
4. When using `redis-sentinel`, the Redis master to use is configured via `STORAGE_SYSTEM_CACHE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`. |