[GitHub] [buildstream] juergbi commented on issue #1540: [bst-1] "Error instantiating artifact cache: Size '' parsed from '/home/fedora/.cache/buildstream/artifacts/cache_size' was not an integer"

[GitBox <gi...@apache.org>]

juergbi commented on issue #1540:
URL: https://github.com/apache/buildstream/issues/1540#issuecomment-986262934


   It's an optimization of the startup time. For cache expiry to work, BuildStream (or buildbox-casd for master) needs to know the disk usage of the cached blobs. Determining the disk usage can take quite a bit of time if a lot of blobs are cached.
   
   buildbox-casd deletes the cache size file on first write (i.e. when it's invalidated), so a crash of buildbox-casd shouldn't cause any problems except that next startup will take longer. And the cache size file is created using atomic rename, so it should never be corrupt, assuming a reasonable filesystem and storage device.
   
   The cached size will be incorrect if anyone were to manually add or remove blobs without going through buildbox-casd. Is this the case you're worried about?
   
   See also https://gitlab.com/BuildGrid/buildbox/buildbox-casd/-/issues/59


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org