Skip to main content

Disconnected node

If a node becomes disconnected from the central node in a Qlik Sense site (that is, if the node fails to synchronize with the central node), the disconnected node serves up to its current allocation of licenses.

If the disconnected node cannot reach the central node within two (2) hours, the node does not allow any new user connections. When the two hour period has passed, it is still possible to connect to the disconnected node from localhost (that is, from the local computer on which the disconnected node is running).

When logging in to a disconnected node from localhost, the following applies:

  • An authentication mechanism that does not require network access (for example, the authentication that is integrated in the Microsoft Windows operating system) is needed.
  • Operations that require acknowledgment by the master Qlik Sense Repository Service (QRS) are disabled.
  • The QRS handles the synchronization when the disconnected node is reconnected to the Qlik Sense site.
  • The Qlik Sense licensing for any other nodes is not affected by the node being disconnected from the central node of the Qlik Sense site.
  • The disconnected node must connect to the central node of the Qlik Sense site at least every five (5) days. If the disconnected node fails to connect to the central node within the given time, it is no longer possible to log in to the disconnected node.

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!