hard20 pts · first answer countscachingconcurrencyredis

Stale value returns after cache delete

With cache-aside, writers update the database and then delete the cache key. Rarely, the cache holds an old value for hours after an update. Which explanation and fix fit best?

A.Redis replicas sometimes apply DEL before SET, so the delete is lost; send writes to the primary with WAITB.A slow reader cached the old row after the writer's delete; use TTLs plus versions or leasesC.The database isolation level is too strict; switch to READ UNCOMMITTEDD.The network partitioned, so the update never reached the database

Discussion 0

Join free to post in the discussion.

Stale value returns after cache delete

Discussion 0

Related questions