forked from TrueCloudLab/restic
6eece31dc3
Failed locking attempts were immediately retried up to three times without any delay between the retries. If a lock file is not found while checking for other locks, with the reworked backend retries there is no delay between those retries. This is a problem if a backend requires a few seconds to reflect file deletions in the file listings. To work around this problem, introduce a short exponentially increasing delay between the retries. The number of retries is now increased to 4. This results in delays of 5, 10 and 20 seconds between the retries.
13 lines
598 B
Text
13 lines
598 B
Text
Bugfix: Fix rare failures to retry locking a repository
|
|
|
|
Restic 0.17.0 could in rare cases fail to retry locking a repository if
|
|
one of the lock files failed to load. The lock operation failed with error
|
|
`unable to create lock in backend: circuit breaker open for file <lock/1234567890>`
|
|
|
|
The error handling has been fixed to correctly retry locking the repository.
|
|
In addition, restic now waits a few seconds between locking retries to
|
|
increase chances of success.
|
|
|
|
https://github.com/restic/restic/issues/5005
|
|
https://github.com/restic/restic/pull/5011
|
|
https://github.com/restic/restic/pull/5012
|