Writes should block when maximum cache size is reached #25
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, maximum cache size is used to determine when the file manager should start evicting files when 'EnableMaxCacheSize' is enabled.
This methodology should be removed as files should be evicted by maximum time in cache only. Instead, writes resulting in reaching/exceeding the maximum cache size setting should block until space has been reclaimed.