The pruning is done through the service thread, milestone by milestone
There are no jobs and no serialization of pending transactions which weren't pruned due to a shut down
because pruning is sequential and the way to determine which milestone was lastly pruned is by checking the first milestone in the database against metadata file initial milestone index
Run with both:
local-snapshots-prunning-enabled
and
local-snapshots-enabled
Fixes #1104
The pruning is done through the service thread, milestone by milestone There are no jobs and no serialization of pending transactions which weren't pruned due to a shut down because pruning is sequential and the way to determine which milestone was lastly pruned is by checking the first milestone in the database against metadata file initial milestone index
Run with both:
local-snapshots-prunning-enabledandlocal-snapshots-enabledset to
true