Laravel邮件队列收件人堆积原因排查求助

Hey there! Let’s troubleshoot that Laravel email queue stacking issue you’re facing. I’ve gone over your code and setup details, so here are some key areas to check and fix:

Looking at your code, you’re creating a single $message instance outside the loop and reusing it for every user. Here’s the catch: Laravel’s Mailable classes are mutable—each time you call to($user) on the same instance, it adds the user to the recipient list instead of replacing it. By the end of the loop, your queue tasks might be carrying multiple recipients, or the queue is getting overloaded with misconfigured tasks.

Fix this by creating a new Mailable instance inside the foreach loop:

foreach($users as $user){
    $message = (new \App\Mail\EmailUpdate(request('subject'), request('message')))->onQueue('emailsDefault');
    \Mail::to($user)->queue($message);
}

Since you suspect this might be the culprit, let’s dig in:

• Check for duplicate users: Run $users->unique('id') before looping to ensure you’re not processing the same user multiple times. Duplicates would create unnecessary queue tasks and slow things down.
• Batch large user sets with chunk(): If you’re working with hundreds/thousands of users, fetching all at once can eat up memory and cause queue backlogs. Use chunking to process in smaller batches:

  // Replace your user query with chunk()
  User::where([/* your filter conditions */])->chunk(100, function ($batch) {
      foreach($batch as $user){
          $message = (new \App\Mail\EmailUpdate(request('subject'), request('message')))->onQueue('emailsDefault');
          \Mail::to($user)->queue($message);
      }
  });
  

• Verify filter accuracy: Double-check where clauses, scopes, or any segmentation logic to ensure you’re only fetching the intended users. Accidentally pulling in extra users will flood your queue.

Even if you followed the docs, small misconfigurations can cause stacking:

• Confirm queue connection: Make sure your .env file has QUEUE_CONNECTION set to database, redis, or another queue driver—not sync (which runs tasks immediately, no queuing).
• Supervisor is listening to the right queue: Your tasks are going to the emailsDefault queue, so your Supervisor command needs to specify this queue. If it’s only listening to the default queue, tasks will pile up. Example Supervisor config command:

  command=php /path/to/your/project/artisan queue:work redis --queue=emailsDefault --sleep=3 --tries=3
  

• Check Supervisor process health: Run supervisorctl status to confirm your queue worker processes are running and not crashing repeatedly. Crashes leave tasks unprocessed.
• Inspect failed queue tasks: Use php artisan queue:failed to see if any tasks are failing repeatedly. Failed tasks (from bad SMTP config, invalid emails, etc.) can clog the queue if retries are enabled.

• Check Laravel logs: Look in storage/logs/laravel.log for queue-related errors (like SMTP connection issues or Mailable exceptions) that might be stopping task processing.
• Test with a small user set: Send to 5-10 test users first to confirm the queue processes tasks correctly without stacking. This helps isolate whether the issue is with scale or core configuration.

内容的提问来源于stack exchange，提问作者Adarsh Sojitra