Issue with multiple consumers - re-delivering in progress jobs
Personne n'a encore pris cette issue.
- Langage dominant
- PHP
- Étoiles
- 36
- Forks
- 22
- Merge moyen
- 20 h 36 min
- PR mergées (30 j)
- 2
Description
Hello,
I'm not sure if I have found a bug or if this just a case of user error.
I am having an issue with running multiple workers on long running jobs (~20 minutes).
When add a message into the queue and then start 2 workers using the following command
bin/cake worker -c process-invoices -p process-invoices
Initially, 1 worker will begin to process the job. However, after about 5 minutes, the other worker also begins to start working on the same job.
I have set $maxAttempts = 1 in the job class.
Next, I tried to bind each processor to an unique name
bin/cake worker -c process-invoices -p process-invoices1
and
bin/cake worker -c process-invoices -p process-invoices2
The message is only picked up by 1 worker, however if another message gets added to the queue, the other worker receives the following error:
[LogicException] Processor was not found. processorName: "process-invoices2" in /var/www/html/vendor/enqueue/enqueue/ArrayProcessorRegistry.php on line 33
And when I don't bind the processor name and run the following command twice to create 2 workers
bin/cake worker -c process-invoices
I receive a similar error:
error: [LogicException] Processor was not found. processorName: "Cake\Queue\Queue\Processor63e2a1884f1c4" in /var/www/html/vendor/enqueue/enqueue/ArrayProcessorRegistry.php on line 33
For reference, the config for the queue is:
'Queue' => [
'process-invoices' => [
'url' => null,
'queue' => 'process-invoices',
'logger' => 'stdout',
'receiveTimeout' => 10000,
'storeFailedJobs' => true,
],
],
I am unable to figure out a method of having multiple workers without the errors or re-processing jobs.
Is there any config setting (visibility timeout) that I am missing to resolve my issues?
Thanks!
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par reproduire le problème avec deux processus worker bin/cake utilisant la configuration process-invoices et une tâche de longue durée. Lisez le point d’entrée du worker et l’échec signalé dans ArrayProcessorRegistry.php, puis comparez le comportement avec des noms de processeur uniques et partagés. Le travail est terminé lorsque plusieurs workers peuvent traiter les tâches en file d’attente sans nouvelle livraison ni erreurs Processor was not found.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- php
- Domaine
- backend, distributed-systems
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100