Alternative to queue worker app bootstrapped in memory just like in octane

[marius-mcp]

https://laravel.com/docs/8.x/queues

"Remember, queue workers, are long-lived processes and store the booted application state in memory. As a result, they will not notice changes in your code base after they have been started. So, during your deployment process, be sure to restart your queue workers. In addition, remember that any static state created or modified by your application will not be automatically reset between jobs."

Is there a way we can change this to opcache like behavior as opposed to octane behavior?

Now I realize what the comparisons between symfony and laravel meant about data clogging.

queue:listen I saw has some issues with handling signals... #47444

UPDATE:

How to disable caching the app in worker command?

[marius-mcp]

Found this https://stackoverflow.com/questions/76462520/how-to-handle-sigterm-signal-on-laravel-8-9-10-deploy-with-docker-containers-in

and taking into account this #49633

#!/usr/bin/env bash
work=true

function stopQueues() {
    echo "Stopping queues..."
    work=false
    #php artisan queue:restart
}

# handle graceful shutdown
trap "" SIGPIPE
trap stopQueues SIGTERM SIGINT SIGHUP

echo "Starting PHP queue workers..."
# SQS_QUEUE
while $work; do
    #php artisan queue:restart
    php artisan queue:work --queue="$(grep -oP 'SQS_QUEUE=\K.*' .env)" --once --sleep=5 --timeout=300
done 

echo "Exit queue  workers..."
exit 0

This will handle signals and execute in a loop the queue:work --once if needed and coupled with opcache and JIT it should be fast enough.

[marius-mcp]

Side note: For queue if supervisord is used, be aware that it might restart the worker after the worker exited and before the container was killed because supervisord is not aware of signals.

This can happen when you have 2 workers started. First one exists and the second one takes longer. Before worker 2 exits, worker 1 is restarted by supervisord and then it might be possible that a job from worker 1 is killed before exiting when the container is killed.

[marius-mcp]

After 4 h of research it hit me: The daemon queue:work "stores the booted application state in memory" BECAUSE IT IS A PHP process not because the app is stored in the cache or in memory on purpose by laravel. So just restarting queue:work command will "invalidate the cached code and static variables".

This should be better explained in the documentation....

So the --once option is enough and there is no need for queue:restart