.Cache entries now refresh as expected 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. 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. To resolve this issue, in {product} 3.1, logic has been added to update the expiration time of cached entries when updated.