The order of operations when loading a value is such:
promise is added for key
value is calculated
keys are added to secondary index
This opens up a race condition, where if someone is to invalidate by tag ID of the entry after it's been added to cache, but before it's been added to secondary index, the entry will not be removed because it's not present in secondary cache yet.
It is questionable how important is this invalidation miss. It is not possible to know before calculating the value if secondary index will be used.
Approaches
We would need some sort of recent tag invalidations check, which would be consulted to drop cached value as it's loaded.
Problem
The order of operations when loading a value is such:
This opens up a race condition, where if someone is to invalidate by tag ID of the entry after it's been added to cache, but before it's been added to secondary index, the entry will not be removed because it's not present in secondary cache yet.
It is questionable how important is this invalidation miss. It is not possible to know before calculating the value if secondary index will be used.
Approaches
We would need some sort of recent tag invalidations check, which would be consulted to drop cached value as it's loaded.