The QVS cluster consist of two servers:Selun-hlg
Load balancing on the Webserver is set to Random
which means that the document is randomly opened on the servers in the cluster:
- CPU with RAM Overload, meaning that the client is directed to the least busy QVS.
- Loaded Document, meaning that the client is directed to the QVS in which the requested document is already loaded.
- Random, meaning that the client is directed to a QVS randomly.
When creating a UserBookmark:
An XML-file with this bookmark is created locally on the user machine (C:\Users\USERNAME\AppData\Roaming\QlikTech\QlikView\Bookmarks) containing the details of this bookmark:
Local bookmarks refers to cluster node instead of cluster name. In above example the bookmark refers to node selun-hlg
Next time the application is opened it could be from the other cluster node. Since the bookmark points to selun-hlg it will not be visible if application opened from su-hlg.
This behaviour is Work As Designed. The local user bookmark is connected to the application by the QVUserBookmarkFile Path, i.e. local bookmarks refers to the server where the document was opened.
For users to be able to use their Local User bookmarks in a clustered environment these bookmarks need to be converted to personal Server bookmarks. These bookmarks is only available when working with the doucment from QlikviewServer and only for authenticated users.
The server bookmarks are stored in a .shared file on the server and is available to the user from all machines where the user is authenicated.
To convert Local User bookmarks to server bookmarks the user can either open the application with Plugin Client and in the Bookmarks More menu select the bookmarks that are to be exported to server bookmarks or open the application in the Desktop client and use the Bookmarks more menu from there.
By clicking Move Local User Bookmarks to Server
the bookmarks will be moved to the .shared file on the server instead of being saved locally on the users machine.
Another resolution is to instead of using Load balancing Random
use Loaded Documents
On the distribution task there is an option to set Document Control:
If this is set to Always be available on one node in combination with Load balancing Loaded Document the user is always directed to the same node in the cluster when the Document is opened.