Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When configuring Bazel Buildfarm, setting actionCacheExpire to be less than casExpire is more reasonable ? #1859

Closed
duanguoxue opened this issue Sep 20, 2024 · 1 comment

Comments

@duanguoxue
Copy link

https://meroton.com/blog/bazel-6-errors-build-without-the-bytes/

@duanguoxue duanguoxue changed the title When configuring Bazel Buildfarm, setting actionCacheExpire to be less than casExpire is more reasonable. When configuring Bazel Buildfarm, setting actionCacheExpire to be less than casExpire is more reasonable ? Sep 20, 2024
@werkt
Copy link
Member

werkt commented Sep 23, 2024

tl;dr: No, this will not improve behavior

casExpire only affects redis key definitions, and has little to do with the expected time that a blob is actually expired and removed from the system.

The default config setting is now (as of #1822) to issue a findMissingBlobs request, which, also by default, will not concern itself with the redis definition, and if a blob is requested from that set later for read, the server will assume best intent and locate+adjust the redis registrations for the blob, even if the casExpire has triggered removal of the worker set.

@werkt werkt closed this as completed Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants