Skip to content

v0.3.0

Choose a tag to compare

@skybleak333 skybleak333 released this 16 Oct 12:48

Third experiment: what queue:work and rabbitmq:consume do while they are paused: in maintenance mode, after SIGUSR2, or with queue:pause.

  • queue:work stops at once on SIGTERM and within --sleep on queue:restart, also while it is paused.
  • rabbitmq:consume acts on SIGTERM and queue:restart only after artisan up or SIGCONT, and runs one more job first. While it is paused, it holds the messages RabbitMQ sends it, up to the prefetch count, so another worker on the same queue gets none of them. It ignores queue:pause.
  • An idle rabbitmq:consume does restart on queue:restart on these versions (vyuldashev/laravel-queue-rabbitmq#587).

Other changes:

  • Every experiment gives its workers a storage directory of their own (LAB_STORAGE) with a file cache, so a manual artisan down doesn't reach them.
  • The event logs also record JobPopping, WorkerPausing and WorkerQueuePaused.
  • The README starts with a summary of the findings and has charts drawn from the event logs.

Checked in CI with PHP 8.3–8.5, Laravel 13.37, php-amqplib 3.7.5 and RabbitMQ 3.13.3. Until vyuldashev/laravel-queue-rabbitmq#680 is released, the package is installed from its branch.