It's not possible to have 2 different versions of the QVS running in a cluster.
I've experienced this in the past, where you can't start the secondary node in the cluster unless it matches the primary node's version.
What situation are you hoping to address with this architectural direction?
This is possible for testing.
All QVSs in a cluster must have the same build number and share the same document root. When upgrading to a new version of QlikView, this is normally not a problem, if all servers are stopped, upgraded, and re-started in one go. However, if not all servers are upgraded at the same time, the build number and document root have to be taken into consideration, since the original cluster is split into two sub-clusters during the upgrade process â€“ one that runs the original version of QlikView and one that runs the new version of QlikView â€“ until all servers have been successfully upgraded to the new version of QlikView. Both sub-clusters share the existing cluster license, including all CALs.
The process for upgrading a single server in a cluster to a new version of QlikView is as follows:
- Open the QlikView Management Console (QMC) on any server in the cluster.
- Fill in the Alternate Build Number and Alternate Document Root fields (see below for details). The field values are automatically propagated to all servers in the cluster.
- Stop the server that is to be upgraded.
- Install the new version of QlikView on the server that was stopped.
- Open the
Settings.inifile (normally located in the
C:\ProgramData\QlikTech\QlikViewServerfolder) on the server where the new version of QlikView was installed.
- Edit the path to the root folder (â€œDocumentDirectoryâ€), so that it points to the same folder as the Alternate Document Root field in the QMC.
- Start the upgraded server