Reclaim may cause excessive extent growth
Reclaim runs more quickly in v3.7.x, and uses free space at a higher rate.
The parameter designed to avoid causing the extents to grow excessively, the ReclaimGem parameter #reclaimMinFreeSpaceMb, was not done at the correct place in 3.6.x or 3.7.x and was therefore not helpful. As a result, under some conditions reclaim may cause unreasonable repository growth, to the point where the extents run out of space and the stone shuts down.
Workaround
Reducing the number of reclaim threads to 1 can help. Avoid heavy reclaim demand, such as after an MFC, when the system is in heavy use.
Unfortunately, due to other bugs, #sleepTimeBetweenReclaimUs and #sleepTimeWithCrBacklogUs are not effective in these versions.
Last updated: 2/21/25