Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
Our setup is:
Qlik Sense enterprise April 2019 patch 1
4 nodes:
We want to set up load balancing rules based on app.owner so that all apps that are owned by super-users will be reloaded and load balanced only by Node 4 and all other apps should be load balanced by Node 1 and Node 2.
Is this possible, and in that case, how do we write the rules?
Best regards
Petter Grundström
How are you defining a super-user? A group? A custom property? A role? Some combination of those three?
A super-user is a member of a specific AD group i.e. user.group
With all things rules related, there are multiple ways of accomplishing this. The way that I'd go about it is:
Will this ensure that the apps owned by the super users are always load balanced by the specific node and that they can't be load balanced by the central node?
Qlik Help says this:
"The default algorithm used for load balancing is round-robin, where the load is evenly distributed between the available nodes on the multi-node site. However, any subsequent sessions from the same user/client will open on the current engine node, instead of following the round-robin."
Which would indicate that if a super user starts a session which is load balanced by the central node, all the subsequent sessions, including ones for apps owned by the super user.
> Will this ensure that the apps owned by the super users are always load balanced by the specific node and that they can't be load balanced by the central node?
In the example the apps own by super users would be available on the node with the name RIM1. You cannot selectively exclude applications from the Central node (this is from the load balancing rule named ResourcesOnCentralNode which is uneditable).
> "The default algorithm used for load balancing is round-robin, where the load is evenly distributed between the available nodes on the multi-node site. However, any subsequent sessions from the same user/client will open on the current engine node, instead of following the round-robin."
> Which would indicate that if a super user starts a session which is load balanced by the central node, all the subsequent sessions, including ones for apps owned by the super user.
So, taking a step back, load balancing rules distribute apps across servers / compute resources. They do not govern what a user can see. That's handled by security rules. With that in mind, with that style of rule, any user who can view an app which is owned by a super user would use the compute resources on RIM1. Any other app which a user can see would use the compute resources on RIM2.