Qlik Sense Apps loading / opening on Central node, despite Load Balancing Rule setupArticle Number: 000052540 | Last Modified: 2019/03/29
Qlik Sense June 2017 and up
Qlik Sense operates based on Consumer Nodes, Central Node, and Reload / Scheduler Node.
With the default set of load balancing rules, and the default Virtual Proxy setup with all nodes added as available engine, any node is a Consumer Node, even the Central one. A Qlik Sense Central Node needs all services installed in order to be able to manage the system, but it should not actually be used as a consumer or reload node. It can be a smaller machine, too, since it will not be needing as much on resources.
In order to set up the Central Node as a proper, manage only, node:
- Remove it from the virtual proxies as an available engine
- Set the Scheduler on the Central to MASTER, and all the Rim nodes to SLAVE.
For troubleshooting around possible issues with this setup, see
Slave scheduler can't reload apps. Fail to reload - message 'No slave-nodes found to execute Task'. or contact Qlik Support.
Have a Question?
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.