--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/daf7aae0-1d75-4153-8fdc-d6e2d1a8b2c3n%40googlegroups.com.
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
Hi Ben, Which Rundeck version are you using?Greetings.
On Friday, April 28, 2023 at 9:38:47 AM UTC-4 ben.k...@redis.com wrote:
Thanks, ya that's the first option I tried. No matter it's value no more than 10 nodes are running in parallel. I can confirm that rundeck recognizable this value change in the system report page but I guess there is another limit somewhere?
Hi Ben,Take a look at this. Try to add "quartz.threadPool.threadCount = 20" parameter on your "rundeck-config.properties" config file and then restart your Rundeck instance.Regards.On Thursday, April 27, 2023 at 5:58:31 PM UTC-4 ben.k...@redis.com wrote:Hey,We noticed when stress testing our ENV that when an execution is started over more than 10 (local executor) nodes only 10 "nodes" are actively running at a time, where the rest are pending in a queue.In this specific use-case all nodes are of type "local executor" so I can't set/edit the thread pool count that you can do with remote-execution.Any ideas on which setting can control the max concurrent-nodes for Rundeck local executor?--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/daf7aae0-1d75-4153-8fdc-d6e2d1a8b2c3n%40googlegroups.com.
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
--
You received this message because you are subscribed to a topic in the Google Groups "rundeck-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rundeck-discuss/YIAqR7SK_fM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/226a24dd-09fe-40d1-bfe3-c6b2cce5d2e6n%40googlegroups.com.
Hi Ben,I tested the "quartz.threadPool.threadCount" successfully on 4.12.1. Set "quartz.threadPool.threadCoun"t with a custom value, e.g.: 20. And restart your instance.2. Then, on your job, set the thread count with the number of nodes that you have in your model source (Edit your job, go to "nodes tab" and then set the Thread Count textbox).3. Save and run your job.If I understood the problem correctly, this approach should achieve your goalRegards.
On Friday, April 28, 2023 at 12:11:46 PM UTC-4 ben.k...@redis.com wrote:
We're running 4.10.1 version
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/2ba9a9a8-4eff-4be7-b0d1-22000b36303en%40googlegroups.com.