CODEWITHSUNDEEP
laravelqueuelumenbeanstalkdforge
JohnSchmidt
JohnSchmidt

Reputation: 9

Beanstalkd running all jobs in the queue simultaneously on forge queue workers

I'm running an API build on Laravel Lumen 5.1, but I can't seem to get the Forge Queue Worker to work properly when using beanstalkd as a driver. It seems to run all the jobs in the queue simultaneously

I'm using the Forge UI to set up the driver

Queue Worker setup

And the .env drivers The .env drivers

The queue system works fine when running it manually without any worker processing it.

If you need any more informations to help me, please just ask!

Upvotes: 0

Views: 576

Answers (1)

Pentium10
Pentium10

Reputation: 208002

The purpose of the message queue is to allow parallel processing. If you have more workers eg: more threads than it will run simultaneously as many jobs.

In order to achieve non simultaneously that is counter intuitive and against the message queue principle. You can achieve that with 1 single worker, but it's not recommended as you don't leverage the power and scalability.

Upvotes: 1

Related Questions