Are there any good reasons to avoid db_record_lock_factory in favour of file_lock_factory for cron job locking? (I'm having trouble working this out from the documentation.)
I'd assume that the performance will be a lot worse, but the lock API documentation explicitly says "locking is not meant to be fast", so presumably this doesn't matter too much.
The reason I'm asking is that we're (very occasionally) seeing cron jobs running twice at the same time and are concerned it might be something to do with file locking. As far as we can see, file locking is generally sound on our setup, but we might prefer to use database locking as it seems simpler and potentially more stable than relying on file locking across a cluster.