Unable to change maximum number of parallel job runs

1,498 views
Skip to first unread message

Alex McNeilly

unread,
Jun 10, 2014, 12:35:01 PM6/10/14
to rundeck...@googlegroups.com

In our current Rundeck installation (version 2.0.3) we are only able to run ten jobs in parallel across all projects which is not always enough.

According to the information on "Scaling Rundeck" we need to change the maximum threadCount value for Quartz scheduler as follows :

Quartz job threadCount

The maximum number of threads used by Rundeck for concurrent jobs is set in the quartz.properties file. By default, this is set to 10.

  • Launcher install: $RDECK_BASE/server/exp/webapp/WEB-INF/classes/quartz.properties

To change the maximum threadCount modify this file and alter the line:

org.quartz.threadPool.threadCount = 20

Set the threadCount value to the max number of threads you want to run concurrently.


The file quartz.properties is empty. We can add the line org.quartz.threadPool.threadCount = 20. However, when we restart Rundeck the file is overwritten and returns to being a blank file again. We cannot seem to increase the maximum number of threads using this method.



Alex McNeilly

unread,
Jun 23, 2014, 4:12:39 PM6/23/14
to rundeck...@googlegroups.com
Tried on a VM with the latest version (2.1.2). Same result. Any changes made to $RDECK_BASE/server/exp/webapp/WEB-INF/classes/quartz.properties are lost on restart.

Alex McNeilly

unread,
Jun 26, 2014, 3:28:07 PM6/26/14
to rundeck...@googlegroups.com


On Tuesday, June 10, 2014 12:35:01 PM UTC-4, Alex McNeilly wrote:


The file quartz.properties is empty. We can add the line org.quartz.threadPool.threadCount = 20. However, when we restart Rundeck the file is overwritten and returns to being a blank file again. We cannot seem to increase the maximum number of threads using this method.




It seems this may depend on the installation method. We were not able to get this to work using the self contained jar launcher.

However, installing using the deb on an Ubuntu VM allowed us to modify quartz.properties and have the change stick after a service restart. The (future) prod server is not debian-based so be trying a few other install methods.

 

Alex Honor

unread,
Jun 26, 2014, 3:44:36 PM6/26/14
to rundeck...@googlegroups.com

Sounds like a bug in the launcher packaging. Might be the quartz.properties template or the config generation is not working.




--
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.
For more options, visit https://groups.google.com/d/optout.



--

Alex Honor

[SimplifyOps, Inc | a...@simplifyops.com ]

Be sure to comment and vote on Rundeck Feature Development!

Reply all
Reply to author
Forward
0 new messages