Unexpected number of reclaim threads when STN_NUM_GC_RECLAIM_SESSIONS is set
A explicit setting for STN_NUM_GC_RECLAIM_SESSIONS is ignored if STN_MAX_GC_RECLAIM_SESSIONS is at the default (0).
When STN_MAX_GC_RECLAIM_SESSIONS is at the default (0), the setting used is computed based on the repository size and is 1, 4, 10 or the number of extents, whichever is greater. STN_NUM_GC_RECLAIM_SESSIONS is also set to this value.
Also note that during restore, the number of reclaim threads is automatically increased ensure reclaim will be able to keep up. This can result in unexpected number of threads still running if you have not restarted the repository after the restore.
Workaround
Explicitly setting STN_MAX_GC_RECLAIM_SESSIONS to a value equal or higher than the setting for STN_NUM_GC_RECLAIM_SESSIONS allows this setting to be used.
After restoring from backup, restart the stone to ensure you have the correct number of reclaim threads.
Last updated: 12/20/24