-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose cronWorkflowWorkers as config item. #11454
Comments
does it mean if I have 9 different cronworkflows set to run hourly that one will be missed? |
Added in #11457 (albeit as an argument, not a config option) |
I believe it's more that there are 8 (lightweight) threads running by default. So if you have 9 cron schedules trigger simultaneously, they all get added to the queue and up to 8 can be processed in parallel (also depends on number of cores and other things running on the CPU etc). @sarabala1979 feel free to correct me as you obviously know this code better than me! |
(^that is also given a single controller instance without any sharding) |
Summary
Currently `cronWorkflowWorkers' was hardcoded. In some scenarios, if the user is using cron workflow heavily, they need more workers to process the cronworkflow.
What change needs making?
Use Cases
When would you use this?
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: