In the case of multiple running bitcoin service instances running in a cluster sharing the same DB, there can only be one instance that is changing/updating the lock, so this feature is to avoid the service running into concurrency and/or conflict issues.
thehenrytsai
commented
4 years ago
In the case of multiple running bitcoin service instances running in a cluster sharing the same DB, there can only be one instance that is changing/updating the lock, so this feature is to avoid the service running into concurrency and/or conflict issues.