Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
Post upgrade to Qlik Sense June 2018 or higher, the following error is logged when attempting to launch multiple (4) tasks at the same time. This can affect manual triggers or scheduled triggers.
"Could not reserve an executor for task"
Reducing the number to two (2) tasks executed at the same time solves the problem, but the server was previously able to run more than that.
System.Scheduler.Scheduler.Master.Slave.SlaveManager DOMAIN\serviceaccount Slave-node NODENAME cannot run task TaskName. Message: Engine not alive
System.Scheduler.Scheduler.Master.Task.TaskSession DOMAIN\serviceaccount Could not reserve an executor for task: No node found for task(name/id) TaskName/TaskIDTaskID
System.Scheduler.Scheduler.Master.Task.TaskSession DOMAIN\serviceaccount Failed to start session 0 TaskName TaskIDTaskID
The issue appears to happen when CPU usage is high. However, the tasks are not getting queued as they should and the fail immediately.
Qlik Sense April 2018 to April 2019
Qlik Sense September 2018 Patch 4
Qlik Sense November 2018 Patch 4
Qlik Sense February 2019 Patch 3
Qlik Sense April 2019 patch 1
Qlik Sense June 2019
See the release notes of the individual version for details on QLIK-94286.
This workaround positively affects environments using the different applicator, and helps taking down the load on the CPU. If CPU usage remains too high, the task will still fail. For instance, this might helpful if AAALR warnings are visible in the logs, but it's worth trying even if none are logged.
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.