This is an architecture question for a two-node Qlik Sense environment.
Is it possible to dedicate one node to do task reloads and another node to handle user sessions?
If so, can anybody show how that would be configured? @Levi_Turner what do you think 🙂
Hi @mwallman ,
I believe this should be possible , may be this article will help
We have three nodes (1 central node 2 rim nodes). We only run the scheduler service on the central node and turned it off on both rim nodes. Additionally, our default proxy load balances on the rim nodes. In this way, our centralized node handles task reloads and users are using rim nodes only. We came up with this based on the below from Qlik help - we basically only have a "master". This works for us given our ram/cpu configuration and # of task reloads.
The Qlik Sense Scheduler Service (QSS) manages the scheduled tasks (reload of Qlik Sense apps or user synchronization) and task chaining. Depending on the type of Qlik Sense deployment, the QSS runs as master, slave, or both on a node.
No, we did not change/add any security/load balancing rules to achieve this.
Hopefully we haven't fooled ourselves into thinking we're doing what we think we're doing. :S However, we tested by installing a specific driver on the central node only. The task that relies on that specific driver reloads on a regular basis and has not failed. We figured if the task reloaded on a rim node the reload would fail because the driver would not be installed on the rim node.
With 2 nodes in a cluster there are two logical possible ways to achieve this:
Option 1: User Access RIM, Reload Central
In this configuration, user sessions will be handled by the RIM node (for short-hand it is common to call this a Consume node or Engine/Proxy node).
Services needed: Engine, Proxy, Repository
Brief config steps:
Option 2: User Access Central, Reload RIM
In this configuration, user sessions will be handled by the Central node and the RIM node will perform application reloads.
Services needed: Engine, Scheduler, Repository
Brief config steps: