Queue worker supervision in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a queue worker that listens to the default queue.

Laravel

php artisan queue:[1]

Drag options to blanks, or click blank then click option'

Astart

Blisten

Cwork

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'listen' instead of 'work' which is a different command.

Using 'start' or 'run' which are not valid artisan queue commands.

The queue:work command starts a queue worker that listens for new jobs on the default queue.

2fill in blank

medium

Complete the code to run a queue worker that processes jobs on the 'emails' queue.

Laravel

php artisan queue:work --queue=[1]

Drag options to blanks, or click blank then click option'

Anotifications

Bjobs

Cdefault

Demails

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong queue name like 'notifications' or 'default'.

Omitting the queue name which defaults to 'default'.

The --queue=emails option tells the worker to process jobs only from the 'emails' queue.

3fill in blank

hard

Fix the error in the supervisor configuration to set the correct command for the queue worker.

Laravel

"command": "php artisan queue:[1] --sleep=3 --tries=3"

Drag options to blanks, or click blank then click option'

Awork

Bstart

Crun

Dlisten

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'listen' instead of 'work' in supervisor config.

Using invalid commands like 'start' or 'run'.

The supervisor config uses queue:work to run the worker as a daemon with options like --sleep and --tries.

4fill in blank

hard

Fill both blanks to configure supervisor to restart the queue worker every 3600 seconds and log output to the correct file.

Laravel

"command": "php artisan queue:[1] --sleep=3 --tries=3 --timeout=90",
"autorestart": true,
"startretries": 3,
"stopwaitsecs": 3600,
"stdout_logfile": "/var/log/laravel/[2].log"

Drag options to blanks, or click blank then click option'

Awork

Blisten

Cworker

Dqueue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'listen' instead of 'work' in the command.

Naming the log file incorrectly or inconsistently.

The command uses queue:work for the worker process. The log file is named 'queue.log' to reflect queue worker logs.

5fill in blank

hard

Fill all three blanks to create a Laravel command that supervises queue workers with a max of 5 processes and a timeout of 120 seconds.

Laravel

supervisor_config = {
  "command": "php artisan queue:[1] --sleep=3 --tries=3 --timeout=[2]",
  "numprocs": [3],
  "autorestart": true
}

Drag options to blanks, or click blank then click option'

Alisten

Bwork

C120

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'listen' instead of 'work' for the command.

Setting timeout or numprocs to wrong values.

The queue:work command runs the worker. Timeout is set to 120 seconds, and numprocs is 5 to run 5 worker processes.

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