Distributed Scheduled Job Locking with Redis

To prevent multiple servers from running the same scheduled job at the same time, a Redis lock is used. The lock is acquired before running the job, and released after it's finished. This prevents duplicate work and potential database issues. To implement this, use a Redis client to set a lock key with a unique token, and then check if the lock was acquired. If not, skip the job. If the lock is acquired, run the job and then release the lock. This can be done using a single Redis command and a Lua script to ensure the lock is released only by the server that acquired it.