Skip to content

Existence Cache serves stale existence after Redis maxmemory eviction #2436

Description

@sravankasu
Remote Execution Failure:
Failed Precondition: status: NotFound, message: "Object xxxx not found in either fast or slow store. If using multiple workers, ensure all workers share the same CAS storage path

When using an Existence Cache that wraps a RedisStore and Redis is configured to use an evicting maxmemory-policy (e.g. allkeys-lru), the existence cache keeps reporting blobs present after Redis evicts the keys causing build failures as shown above.

Seems like after the change in #1947 the remove-callbacks in redis_store.rs makes it a silent no-op, refer comment here.

Seems like that comment may not be true as already noted here.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions