Conversation
| Takes a `number` which specifies the default number of a specific job that can be running at | ||
| any given moment. By default it is `5`. | ||
|
|
||
| The concurrency parameter is only important when the job takes longer than its |
There was a problem hiding this comment.
Pretty sure this is incorrect. Gonna throw together a minimal repo to try and confirm.
There was a problem hiding this comment.
Ok, I've thrown this together: https://github.com/wingsbob/agenda-concurrency-example
You can run with different default concurrency levels by setting the environment variable CONCURRENCY. The lock time is left as the default (10 mins), so that's definitely not coming into effect.
Agenda#every might not be the best example for concurrency, as it creates single type jobs, which seem to be semi-unique
|
|
||
| * Multiple queues don't process the same job | ||
| * The same job doesn't get run again before it has finished. For example, if a job | ||
| is scheduled to run [`every`](#everyinterval-name-data-options-cb) 5 seconds but |
There was a problem hiding this comment.
maybe use Job#repeatEvery for this example
|
Is this able to be updated or should we close this? |
|
We are actively working on Agenda 6.x which includes a complete TypeScript rewrite with many improvements. This issue is being closed as part of our migration. If this is still relevant after 6.x is released, please open a new issue. Thank you for your patience! |
I hope examples will greatly help newcomers understand how Agenda works!