Max concurrent reloads reached, but more reloads are starting. QlikView 11.20

[NicolasRivas]

Hello,

I have the max concurrent reload value set to 9, because the server have 10 virtual processors, but I now have 46 tasks running simultaneously. 
I also have the Max number of simultaneous QlikView engines for distribution set to 4
and Max number of simultaneous QlikView engines for administration set to 7.

[rzenere_avvale]

Hey @NicolasRivas ,

On which version of QlikView is your environment? Also, by "running simultaneously" you mean that they are actually in "started" or you're considering "queued" too?

Riccardo

[NicolasRivas]

Hello!

The version is 11.2, and yes, they are in "started".

[rzenere_avvale · Accepted solution]

From what I can remember, on QV 11.2 those configurations were NOT honored all the time
This changed with QV 12.1, where the way QV manages reload task was improved (i.e. QlikView Tasks are not executed as expected and are shown in status Queued )

Since QV 11.2 is not supported anymore (see QlikView Product Lifecycle), could you consider upgrading your environment?
Please consider also this kb article before upgrading: QlikView 11.20 End of Support Upgrade: Known Issues and changes in product behavior 

Riccardo

[Maria_Halley · Accepted solution]

 @NicolasRivas 

QlikView, any version, can only run as many simultaneous jobs as you have engines. They might be set to running, but they are probably waiting for an engine. You can check in the task logs, it will say how many engines are used, and if we had to wait.

New jobs will  also get started even there are no available resources. 

If you have to many jobs running at the same time, you should space them out over time.

But as @rzenere_avvale said, this was changed in QlikView 12.0

Below are two great articles on the subject.

Max number of simultaneous engines

Scaling the publisher

[Maria_Halley]

I'm moving this to the QlikView management board instead 

[Maria_Halley]

@NicolasRivas

Was the above suggestions helpful?

[NicolasRivas]

Hello, 

Sory for the delay , how do i know in the log if they are waiting for the engine?, I looked at the logs and some tasks are in "Reloading..." others in "Slow down logging. log every <n> seconds".  and others in "Opening <file path>"

[Chip_Matejowsky · Accepted solution]

Hi @NicolasRivas,

The task log will record the number of QVB engines in use and total available engines. This log will also record if it is waiting for a QVB engine. Article No QlikView Engine was available after waiting for 45 minutes - QlikView reload tasks are not trigge...details this.  So you'll want to see if the reload tasks are at or near using all available QVB engines. See the below snippet from a task log taken from my lab QVS/Pub server as an example.

20220309T083124.163-0500 Information Opening "C:\ProgramData\QlikTech\SourceDocuments\Change category test.qvw"
20220309T083124.165-0500 Information Allocating new QlikView Engine. Current usage count=0 of 4 (of type non-reader).
20220309T083124.165-0500 Information Max retries:5
20220309T083124.165-0500 Information Attempt:01
20220309T083128.567-0500 Information Opened the QlikView Engine successfully. ProcessID=10036
20220309T083128.573-0500 Information Allocated QlikView Engine successfully. Current usage count=1 of 4 (of type non-reader). Ticket number=39.

Best Regards