restic

Commit Graph

Author	SHA1	Message	Date
Michael Eischer	f490288738	lock: freeze backend operations while refreshing stale lock Freeze new backend operations while trying to refresh a stale lock.	2023-07-22 19:55:44 +02:00
Michael Eischer	d05f6211d1	lock: Do not limit backend concurrency for lock files restic must be able to refresh lock files in time. However, large uploads over slow connections can cause the lock refresh to be stuck behind the large uploads and thus time out.	2023-05-08 19:04:46 +02:00
Michael Eischer	ebba233a3a	backend/sema: rename constructor to NewBackend	2023-04-22 12:32:57 +02:00
Michael Eischer	f27750e270	backend/sema: rename type to connectionLimitedBackend	2023-04-21 22:53:09 +02:00
Michael Eischer	6042df075f	migrations: Fix S3 backend detection	2023-04-14 22:32:16 +02:00
Michael Eischer	8e1e3844aa	backend: factor out connection limiting and parameter validation The SemaphoreBackend now uniformly enforces the limit of concurrent backend operations. In addition, it unifies the parameter validation. The List() methods no longer uses a semaphore. Restic already never runs multiple list operations in parallel. By managing the semaphore in a wrapper backend, the sections that hold a semaphore token grow slightly. However, the main bottleneck is IO, so this shouldn't make much of a difference. The key insight that enables the SemaphoreBackend is that all of the complex semaphore handling in `openReader()` still happens within the original call to `Load()`. Thus, getting and releasing the semaphore tokens can be refactored to happen directly in `Load()`. This eliminates the need for wrapping the reader in `openReader()` to release the token.	2023-04-14 22:32:15 +02:00

6 Commits