Writes should block when maximum cache size is reached #25

New Issue

2024-12-10T12:55:27-06:00

sgraves commented

2024-12-10 12:55:27 -06:00

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.

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.

sgraves added this to the v2.0.3-rc milestone 2024-12-10 12:55:27 -06:00

sgraves added the enhancement label 2024-12-10 12:55:27 -06:00

sgraves referenced this issue from a commit

2024-12-18 16:34:51 -06:00

Writes should block when maximum cache size is reached #25

sgraves referenced this issue from a commit

2024-12-18 16:34:51 -06:00

Writes should block when maximum cache size is reached #25

sgraves referenced this issue from a commit

2024-12-18 16:34:51 -06:00

Writes should block when maximum cache size is reached #25

sgraves referenced this issue from a commit