diff options
author | talyz <kim.lindberger@gmail.com> | 2022-09-19T07·30+0200 |
---|---|---|
committer | talyz <kim.lindberger@gmail.com> | 2022-09-19T11·28+0000 |
commit | 28417afbb4d8776501f9ae3ecead5859707488b9 (patch) | |
tree | dcb243f44d6c8f428ab8959cf188890e4a37aa4e /tools/magrathea/mg.scm | |
parent | adf092a26be9da18448e96e1e6198d543d187c63 (diff) |
fix(nixery): Avoid race when the same image is fetched in parallel r/4924
Remove a race condition which appears when uploadHashLayer is called with the same key from multiple threads simultaneously. This can easily happen when the same image path is requested by multiple clients at the same time. When it does, a 500 status is returned and the following error message is logged: { "context": { "filePath": "github.com/google/nixery/builder/builder.go", "lineNumber": 440, "functionName": "github.com/google/nixery/builder.uploadHashLayer" }, "error": "rename /var/lib/nixery/staging/<hash> /var/lib/nixery/layers/<hash>: no such file or directory", "eventTime": "...", "layer": "<hash>", "message": "failed to move layer from staging", ... } To solve this issue, introduce a mutex keyed on the uploaded hash and move all layer caching into uploadHashLayer. This could additionally provide a small performance benefit when an already built image is requested and NIXERY_PKGS_PATH is set, since symlink layers and config layers are now also cached. Change-Id: I50788a7ec7940cb5e5760f244692e361019a9bb7 Reviewed-on: https://cl.tvl.fyi/c/depot/+/6695 Reviewed-by: tazjin <tazjin@tvl.su> Tested-by: BuildkiteCI
Diffstat (limited to 'tools/magrathea/mg.scm')
0 files changed, 0 insertions, 0 deletions