Files
zot/pkg/storage
shcherbak 89f7e24d20 fix(storage): release global write lock during blob restore I/O (#4089)
* fix(storage): release global write lock during blob restore I/O

Restore-deduped-blob reads/writes no longer hold the global storage write
lock for the duration of slow S3 GETs, only for the final write. Adds a
restore-complete marker so subsequent dedupe=false startups can skip the
restore scan, and hardens DedupeTaskGenerator's completion tracking against
races between in-flight restore tasks and Reset().

Signed-off-by: shcherbak <ju.shcherbak@gmail.com>

* test(storage): reuse ThreadSafeLogBuffer instead of duplicate syncBuffer

---------

Signed-off-by: shcherbak <ju.shcherbak@gmail.com>
2026-06-15 09:48:56 +03:00
..
2026-05-11 09:29:05 +03:00

zot currently supports two types of underlying filesystems:

  1. local - a locally mounted filesystem

  2. remote - a remote filesystem such as AWS S3

The cache database can be configured independently of storage. Right now, zot supports the following database implementations:

  1. BoltDB - local storage. Set the "cloudCache" field in the config file to false. Example: examples/config-boltdb.json