Queue worker supervision in Laravel - Step-by-Step Execution

Concept Flow - Queue worker supervision

Start Supervisor

↓

Launch Queue Worker

↓

Worker Processes Jobs

↓

Worker Crashes or Stops?

No→Continue Processing

Yes↓

Supervisor Detects Failure

↓

Restart Worker

↓

Loop Back to Worker Processes Jobs

The supervisor starts and launches a queue worker. The worker processes jobs continuously. If the worker crashes or stops, the supervisor detects this and restarts the worker, ensuring continuous job processing.

Execution Sample

Laravel

php artisan queue:work
# Supervisor monitors this process
# Restarts if it stops unexpectedly

This command runs a queue worker that processes jobs. The supervisor watches this worker and restarts it if it stops.

Execution Table

Step	Action	Worker Status	Supervisor Action	Output
1	Start Supervisor	No worker running	Launch worker process	Worker started
2	Worker processes job #1	Running	Monitor worker	Job #1 completed
3	Worker processes job #2	Running	Monitor worker	Job #2 completed
4	Worker crashes unexpectedly	Stopped	Detect failure	Worker stopped unexpectedly
5	Supervisor restarts worker	Restarting	Launch new worker process	Worker restarted
6	Worker processes job #3	Running	Monitor worker	Job #3 completed
7	Worker processes job #4	Running	Monitor worker	Job #4 completed
8	Supervisor continues monitoring	Running	No action needed	Worker stable
9	Supervisor stopped manually	Stopped	Stop worker and supervisor	All stopped

💡 Supervisor stopped manually, ending worker supervision and job processing

Variable Tracker

Variable	Start	After Step 1	After Step 4	After Step 5	Final
Worker Status	No worker	Running	Stopped	Running	Stopped
Supervisor Action	Idle	Launching worker	Detecting failure	Restarting worker	Stopped

Key Moments - 3 Insights

Why does the supervisor restart the worker after it crashes?

Because the execution_table row 4 shows the worker stopped unexpectedly, and row 5 shows the supervisor detects this and restarts it to keep jobs processing.

What happens if the worker is running normally?

As seen in rows 2, 3, 6, and 7, the supervisor just monitors the worker without restarting it.

How does the supervisor know when to stop?

Row 9 shows the supervisor is stopped manually, which stops both the supervisor and the worker.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what is the worker status?

A Running

B Restarting

C Stopped

D Idle

💡 Hint

Check the 'Worker Status' column at step 4 in the execution_table.

At which step does the supervisor restart the worker?

A Step 5

B Step 4

C Step 3

D Step 6

💡 Hint

Look for 'Supervisor restarts worker' in the Action column of the execution_table.

If the worker never crashes, how would the supervisor action column change?

A It would keep restarting the worker

B It would keep monitoring without restarting

C It would stop monitoring

D It would stop the worker

💡 Hint

Refer to rows 2, 3, 6, and 7 where the worker runs normally and supervisor only monitors.

Concept Snapshot

Queue worker supervision in Laravel:
- Supervisor starts and monitors queue workers
- Workers process jobs continuously
- If a worker crashes, supervisor detects and restarts it
- Ensures reliable, continuous job processing
- Manual stop ends supervision and workers

Full Transcript

In Laravel, queue worker supervision means a supervisor process starts and watches over queue workers. These workers handle jobs from the queue. If a worker crashes or stops unexpectedly, the supervisor notices this and restarts the worker automatically. This keeps job processing running smoothly without manual intervention. The supervisor continues monitoring until it is stopped manually, which also stops the workers. This system helps keep background job processing reliable and continuous.

Practice

1. What is the main purpose of using Supervisor with Laravel queue workers?

easy

A. To automatically restart queue workers if they stop unexpectedly

B. To speed up the execution of queue jobs

C. To log all queue jobs to a database

D. To convert queue jobs into synchronous tasks

Solution

1. Step 1: Understand Supervisor's role

   Supervisor monitors processes and restarts them if they stop.

2. Step 2: Apply this to Laravel queue workers

   Laravel queue workers run background jobs; Supervisor ensures they keep running.

3. Final Answer:

   To automatically restart queue workers if they stop unexpectedly -> Option A

4. Quick Check:

   Supervisor restarts workers automatically [OK]

Hint: Supervisor restarts stopped workers automatically [OK]

Common Mistakes:

• Thinking Supervisor speeds up job execution
• Confusing logging with supervision
• Believing Supervisor makes jobs synchronous

2. Which of the following is the correct Supervisor configuration directive to specify the command to run a Laravel queue worker?

easy

A. run=php artisan queue:work

B. command=php artisan queue:work

C. execute=php artisan queue:work

D. start=php artisan queue:work

Solution

1. Step 1: Recall Supervisor config syntax

   Supervisor uses 'command=' to specify the process command.

2. Step 2: Match with Laravel queue worker command

   Laravel queue worker runs with 'php artisan queue:work'.

3. Final Answer:

   command=php artisan queue:work -> Option B

4. Quick Check:

   Supervisor uses 'command=' for process commands [OK]

Hint: Supervisor config uses 'command=' for commands [OK]

Common Mistakes:

• Using 'run=' instead of 'command='
• Confusing 'execute=' or 'start=' as valid directives
• Omitting the full artisan command

3. Given this Supervisor config snippet:

[program:laravel-worker]
command=php /var/www/artisan queue:work --sleep=3 --tries=3
numprocs=1
autostart=true
autorestart=true
user=www-data

What happens if the Laravel queue worker process crashes?

medium

A. Supervisor will restart the worker automatically

B. The worker will remain stopped until manually restarted

C. Supervisor will log the crash but not restart the worker

D. The worker will restart only if autostart is false

Solution

1. Step 1: Check 'autorestart' setting

   autorestart=true means Supervisor restarts crashed processes automatically.

2. Step 2: Understand autostart role

   autostart=true means the worker starts on Supervisor start, but restart depends on autorestart.

3. Final Answer:

   Supervisor will restart the worker automatically -> Option A

4. Quick Check:

   autorestart=true means auto restart on crash [OK]

Hint: autorestart=true means auto restart on crash [OK]

Common Mistakes:

• Confusing autostart with autorestart
• Assuming manual restart is needed
• Thinking Supervisor only logs crashes

4. You configured Supervisor to run Laravel queue workers but notice workers are not restarting after failure. Which of these is the most likely cause?

medium

A. The 'numprocs' option is set to 0

B. The 'command' option is missing the '--tries' flag

C. The 'user' option is set to 'root'

D. The 'autorestart' option is set to false or missing

Solution

1. Step 1: Identify why workers don't restart

   Workers won't restart if 'autorestart' is false or missing.

2. Step 2: Check other options' impact

   'numprocs=0' disables processes, 'user=root' is allowed but not recommended, '--tries' controls job retries, not restarts.

3. Final Answer:

   The 'autorestart' option is set to false or missing -> Option D

4. Quick Check:

   autorestart=false stops auto restart [OK]

Hint: Check 'autorestart' to fix no restart issue [OK]

Common Mistakes:

• Confusing job retry with process restart
• Thinking 'user=root' causes restart failure
• Assuming '--tries' affects Supervisor restart

5. You want to run multiple Laravel queue workers supervised by Supervisor to handle high job volume. Which configuration change is best to achieve this?

hard

A. Set 'numprocs' to 1 and increase '--sleep' time in the command

B. Create multiple Supervisor config files each with one worker and same program name

C. Set 'numprocs' to the number of workers needed and use '%(program_name)s_%(process_num)s' in 'process_name'

D. Use 'autostart=false' and manually start each worker process

Solution

1. Step 1: Understand running multiple workers

   Supervisor can run multiple processes with 'numprocs' and unique names.

2. Step 2: Use 'process_name' for unique worker IDs

   Using '%(program_name)s_%(process_num)s' creates unique names for each worker.

3. Final Answer:

   Set 'numprocs' to the number of workers needed and use '%(program_name)s_%(process_num)s' in 'process_name' -> Option C

4. Quick Check:

   Multiple workers = numprocs + unique process_name [OK]

Hint: Use numprocs and unique process_name for multiple workers [OK]

Common Mistakes:

• Duplicating config files with same program name
• Increasing sleep time reduces throughput
• Disabling autostart prevents automatic worker start