To run Laravel queue workers efficiently, choose a reliable driver like Redis or database, configure them properly in .env and config/queue.php. Use optimized Artisan commands with --tries, --timeout, and --sleep settings, and manage workers via Supervisor for stability. Monitor failed jobs, handle memory leaks by restarting workers, adjust Redis visibility timeout to avoid duplication, and clear cache after deploying changes. 1. Choose Redis or database driver for production. 2. Set QUEUE_CONNECTION in .env and verify connection details in config/queue.php. 3. Run queue:work with --queue, --tries=3, --timeout=90, --sleep=5. 4. Use Supervisor for process monitoring. 5. Retry failed jobs with queue:retry and log them via failed_jobs table. 6. Restart workers periodically to prevent memory leaks. 7. Adjust Redis visibility timeout to prevent job duplication. 8. Clear config cache after updating job classes.

When you're running background jobs in Laravel, setting up queue workers properly is key to making sure tasks get processed efficiently without delays or errors. The core idea is to keep the worker running smoothly and avoid common pitfalls like memory leaks or job duplication.

Choosing the Right Queue Driver

Laravel supports several queue drivers — Redis, database, Beanstalkd, Amazon SQS, and even synchronous processing for local testing. For production setups, Redis or database are commonly used because they’re reliable and easy to manage.

• Redis offers better performance and built-in support for things like retries and delayed jobs.
• Database driver works well too, especially if you already have a MySQL or PostgreSQL setup and don’t want extra dependencies.

Make sure your .env file points to the right driver:

QUEUE_CONNECTION=redis

Also, double-check your config/queue.php to set the correct connection details like host, port, and queue name.

Running the Worker Efficiently

Once your driver is configured, start the worker using Artisan:

php artisan queue:work --queue=default

But that’s just the basic command. Here are some useful flags to consider:

• --tries: Specify how many times a failed job should be retried before being marked as failed permanently. Usually 3 tries is a good default.
• --timeout: Set a maximum time (in seconds) a job can run before it's killed and retried. Be realistic here — too short and your jobs might get cut off; too long and you risk blocking other tasks.
• --sleep: How long the worker should wait before checking for new jobs when the queue is empty. A value between 3 and 10 seconds is typical.

For example:

php artisan queue:work --queue=default --tries=3 --timeout=90 --sleep=5

And don’t forget to use a process monitor like Supervisor or PM2 to make sure the worker keeps running even after a crash or server reboot.

Monitoring and Debugging Common Issues

Even with everything set up, things can go wrong. Jobs might fail silently, get stuck, or take longer than expected. Here’s what to watch out for:

• Failed jobs: Use php artisan queue:retry all to retry all failed jobs or specify a particular ID. You can also log failed jobs by creating a failed_jobs table via migration.
• Memory leaks: Workers can accumulate memory over time, especially if you're doing heavy operations inside jobs. Restarting the worker every few hours helps. You can do this automatically using Supervisor's autorestart option.
• Job duplication: If you're using Redis and notice duplicate jobs, check your visibility timeout settings. Jobs reappear in the queue if they aren't acknowledged quickly enough.

One thing people often miss is clearing cache after updating job classes. Always run php artisan config:clear or restart the worker after deploying changes.

That’s basically it. It doesn’t have to be complicated, but getting these small details right makes a big difference in keeping your queue system stable and responsive.

The above is the detailed content of Setting up Queue Workers in Laravel.. For more information, please follow other related articles on the PHP Chinese website!