concurrent jobs limited

[Rainer]

Hi there, 

I noticed when running more than three jobs / templates in parallel the additional started jobs will remain in status "pending". The pending job will be started when another one is finished.  

In our environemnt there is one instance group, including one instance which saying capactiy 100% with 3 concurrent jobs (66% with 2 Jobs) 

I changed the forks value from default (5) to 10, but this did not change the behaviour regarding concurrent running jobs. 

We are using AWX (17.0.1) in a docker container environment. I know it is not up to date. Any Ideas how to increase concurrent jobs ? 10 should be sufficient, I don*t see any resource / perfromance issues. 

Many Thanks

Rainer

[AWX Project]

can you set "allow_simultaneous" to true on the job template through the API? (also called enable concurrent jobs in the GUI). By default this is turned off

[Rai Ner]

The Issue appeares with different templates running at the same time.

For  testing I used one template and set it to "allow simultaneous" and this worked fine and allowed three parallel runs at the same time but not more. 

--
You received this message because you are subscribed to a topic in the Google Groups "AWX Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/awx-project/gNdPvs_r5kA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to awx-project...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/ebe87f92-331d-408f-8c0c-f306aced1c93n%40googlegroups.com.

[Rainer]

My solution was to change the forks value of a template. Prevously I used the default forks value of 5 for each template, which allowed three parallel template executions (no matter how many target hosts per template). 

Since I have several templates running against only one target host I can set the forks value to 1. This enables to run more than three templates.