QMC Task Execution Fails to Show Task Started

[qvd1rkqv]

When I click the start icon to start task manually the QMC will not show it running.  When I look at the Task Details for the  task it shows the task is "running".  We've been experiencing this for some time.  Any guidance is appreciated. 

QlikView May 2021 SR2.  The QVPR is on the same server as the Management Service.  

[Chip_Matejowsky]

Hi @qvd1rkqv,

The scenario you're describing typically indicates that there are communication/synchronization issues between QlikView Management Service (QMS) and QlikView Distribution Service (QDS). Do you have Publisher enabled? Is this a single QDS node or is it a QDS cluster? If cluster, how many nodes?

The whitepaper Scaling QlikView Publisher is a great resource for issues such as this. Suggest that you review it and consider some of the settings within. Ping back if you have specific questions.

Best Regards

[qvd1rkqv]

Hi @Chip_Matejowsky , 

Thanks! Yes we have a 2 node QDS cluster.  I'll review the whitepaper. 

[Chip_Matejowsky]

Great! Suggest you note the sections on Disk Latency, Application Data Folder, Source Data Folder, Best Practices, and QVDistribution.exe.config file. 
Post back if you have questions.

Best Regards

[qvd1rkqv]

@Chip_Matejowsky a clarifying question please.  From the Scaling QlikView Publisher document.  The part about:

“TaskResultCacheUpdateMaxTasksPerThread,” defaults to “0”, which allows for automatic calibration of the number of tasks sent per thread towards the Task Results file. In environments with 300 or more tasks in total, it is recommended to disable automatic calibration as otherwise the QlikView Distribution Service process will spawn a lot of threads when trying to update the files, which in turn generates a higher than desirable load on the underlying file system. Setting it to a value that is higher than the total amount of tasks configured in the system forces the Scaling QlikView Publisher | 11 11 QlikView Distribution Service to only use one thread. If the QlikView Distribution Service spawns many threads, it leads to the QlikView Distribution Service process consuming more CPU resources than it strictly needs to. This is visible in the Windows task manager by observing the CPU consumption for the QlikView Distribution Service process.

Our environment for this cluster has approximately 900 tasks.  Does this mean that changing this to 1000 would be appropriate?  Thanks!

[Chip_Matejowsky · Accepted solution]

Hi @qvd1rkqv,

The scenario you're describing typically indicates that there are communication/synchronization issues between QlikView Management Service (QMS) and QlikView Distribution Service (QDS)

The whitepaper Scaling QlikView Publisher is a great resource for issues such as this. Suggest that you review it and consider some of the settings within. Ping back if you have specific questions.

A value of 1000 would be appropriate for this configuration in my opinion. It would also allow for more tasks as well. 

Since you're running so many Publisher tasks, you also may want to consider adding a 3rd Publisher node to the environment.

Best Regards