Cause: The new time-based metadata cache entry expiration logic did not include logic to update the expiration time on already-cached entries being updated in place. Consequence: Cache entries became permanently stale after expiration, leading to a performance regression as metadata objects were effectively not cached and always read from the cluster. Fix: Logic was added to update the expiration time of cached entries when updated. Result: