Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION

Qlik Sense Reload Jobs Stuck as Queued

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Frank_S
Support
Support

Qlik Sense Reload Jobs Stuck as Queued

Last Update:

Jun 28, 2023 1:57:03 PM

Updated By:

Frank_S

Created date:

Jun 21, 2023 4:20:24 PM

 

Environment

  • Qlik Sense On Windows
  • All supported versions

 

Issue Reported

You have been running Qlik Sense normally for quite some time. Over time you have accumulated an abundance of reload tasks configured in your Qlik Sense QMC.

Recently however, you have noticed that Qlik Sense QMC reload tasks are in the following state:

  • Running reload jobs never complete and stuck in a 'started' triggered state
  • Remaining reload jobs are in a 'queued' status
  • The only way to get reload tasks completed are through restart of Qlik Sense services

 

Resolution

To resolve the issue, it is recommended to add an additional scheduler node (or nodes) in order to manage the ever increasing number of reload tasks in the affected Qlik Sense environment.

As time goes on, add additional scheduler nodes in proportion to the increasing number of reload tasks added/deployed in your environment.

 

Cause 

The existing Qlik Sense scheduler nodes simply cannot manage the additional burden placed upon it by ever increasing reload tasks.

 

Related Content

Concurrent Reload Settings in Qlik Sense Enterprise

 

Internal Investigation ID

QB-20013

Comments
ismailk94
Contributor II
Contributor II

Hi!

Thanks for sharing.
We are experiencing these exact issues on QlikCloud. Do you have any recommendations on how to solve the issues on QlikCloud?

Sincerely,
Ismail

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @ismailk94 

Queues in Qlik Cloud (or on Windows) are not an issue per se. On your on-prem install, this would mean the nodes used are not sufficiently scaled. In Qlik Cloud, you are meeting the normal queuing situation.

We recommend looking into our reload best practices to see how you can improve the situation.

If you have a high number of queued and executing data reload processes (and additional concurrent CPU and memory-intensive processes), you might notice that some reload processes execute, in some cases, noticeably after their scheduled start time. See Scheduling a Reload.

Should you suspect an issue (such as none of your tasks executing at any point or remaining queued until they time out repeatedly), I recommend checking the Qlik Cloud status page first, verifying if Qlik is aware of an ongoing issue. 

All the best,
Sonja 

BTIZAG_OA
Creator
Creator

Hello there, 

How can i identify this with logs that i need more schedule nodes?

Is it possible to see how many remaining cores left for upcoming tasks? If yes which log folder?

Is it possible to measure the burden of tasks? some of them complete in 1 min and some of them complete in 1hour they are probably not same when it comes to CPU/Memory.

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @BTIZAG_OA 

You can find information on what is logged where in Troubleshooting Qlik Sense Enterprise on Windows using logs. Monitoring applications can be built based on these log files to help you answer these questions. And example app can be found in LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs.

If you need more direct assistance, I suggest posting what you are looking to accomplish in our Qlik Sense Management and Deployment forum, where your knowledgeable Qlik peers and our support agents can directly engage with you.

All the best,
Sonja 

Contributors
Version history
Last update:
‎2023-06-28 01:57 PM
Updated by: