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

[6.2.0]Clear all remote metadata if any of them are evicted from remote cache #17770

Merged
merged 2 commits into from
Mar 15, 2023

Commits on Mar 14, 2023

  1. Clear all remote metadata if any of them are evicted from remote cache

    With TTL based discarding and upcoming lease extension, remote cache eviction error won't happen if remote cache can guarantee the TTL. However, if it happens, it usually means the remote cache is under high load and it could possibly evict more blobs that Bazel wouldn't aware of. Following builds could still fail for the same error (caused by different blobs).
    
    This PR changes to remove all remote metadata when the remove cache eviction error happens (which should be rare with the help from TTL based discarding and lease extension) to make sure next incremental build can success.
    
    Part of bazelbuild#16660.
    
    Closes bazelbuild#17747.
    
    PiperOrigin-RevId: 516519657
    Change-Id: Ia99770b9d314ca62801b73dc96d09ed8ac2233f6
    coeuvre authored and ShreeM01 committed Mar 14, 2023
    Configuration menu
    Copy the full SHA
    b0485cf View commit details
    Browse the repository at this point in the history

Commits on Mar 15, 2023

  1. Configuration menu
    Copy the full SHA
    9def25a View commit details
    Browse the repository at this point in the history