Within a multi-node site, one instance of the Qlik Sense Repository Service (QRS) runs on each node. The QRS running on the central node is considered to be the master. The master QRS has direct access to the central repository database, whereas other QRSs only have access to a local repository database on the node where they are running. The master QRS synchronizes the central repository database and the local repository databases. For information on the synchronization procedure, see Synchronization.
The node that is considered to be the central node is installed first. Then, another node can be added to the central node in order to add capacity and resilience, or to move Qlik Sense apps onto a specific node or for a particular set of services. Each node requires a QRS.
On the central node, it is recommended to have a dedicated Qlik Sense Proxy Service (QPS) and a dedicated Qlik Sense Engine Service (QES) that are used specifically for the Qlik Management Console (QMC) and not for the hub.
In addition, the central node must have the Qlik Sense Scheduler Service (QSS) installed even if more QSS nodes are added. This is because the QSS on the central node is considered to be the master QSS, which coordinates all QSS activities within the site.
Learn more
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!