Replies: 1 comment
-
That retry after could be referencing the messaging service not the worker. The worker processes only what the messaging system gives it to process. Based on this the retry after refers to the max amount of time a job is waited for until it is considered not processed by the messaging system. We set this to max 5 mins in our jobs because that is the max time docker waits for a job to complete in a scale down or deploy scenario. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In the docs (https://laravel.com/docs/12.x/queues) there are many references to a retry_after parameter in config/queue.php, yet there is no counterpart if I'm calling
queue:work
via CLI. Am I forced to specify env variables and then pass them to the config?I found something about backoff, but doesn't seem to be the exact same thing. Even if so, why two different names?
framework/src/Illuminate/Queue/Console/WorkCommand.php
Line 33 in 1b0051d
Beta Was this translation helpful? Give feedback.
All reactions