Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everyone who's reading this!
I have simple question but cannot find anything online about this.
We have two QlikView environments, one test environment and one production environment.
In the test environment we are able to change Max number of simultaneous QlikView engines for distribution.
In the live environment we are unable to change the Max number of simultaneous QlikView engines for distrubiton.
On the test and production environment we have different licenses, the test environment has NUMBER_OF_CLUSER_NODES.;2;; and the production environment has NUMBER_OF_CLUSER_NODES;1;;.
The test environment.
The production environment.
If this is an license issue is there a workaround to upscale the Max Simultaneous Engines?
Thanks in advance!
HI,
OK, the issue is that someone has enabled the Distribution Groups. The files for this are stored in C:\ProgramData\QlikTech\ManagementService\DistributionGroups.
Being you do not have cluster QDSs I would stop the QMC service, and rename DistributionGroupDefinition.xml to DistributionGroupDefinition.Template.xml. Then you can make the change in the QMC.
If you want to keep the DistributionGroupDefinition.xml just make your settings in this file.
Bill
Hi,
I have not seen anything in the license that would restrict it. Also, looking at the cluster count, are you sure you have the right license assigned to the correct system?
Hi Bill,
Thanks for your reply,
If it isn't a license issue do you maybe know what else can cause this issue?
Both QlikView versions are the same, build 12.70.20000.0.
AFAIK is the number of engines (regardless to which task-type) not related to the licences but to the (available) number of cores and by any execution to the CPU/RAM consumption. Beside the qmc there are various configurations within the config-files to control this. There might be also options to disable some configurations maybe also depending to each other in a certain way - but don't be able to change qmc-settings hints more for an issue with the access rights to these settings respectively that the services couldn't communicate with each other - by a distributed cluster installation it's not always trivial.
- Marcus
Hi @marcus_sommer,
Thanks for your reply!
Tomorrow I will check if I can find anything in the config files.
If I can find anything I'll let you know asap and mark your answer as a solution! Thanks again.
Hi @Mika_2000,
The NUMBER_OF_CLUSTER_NODES provision in the License Enablement File (LEF) refers to how many QlikView Server (QVS) nodes are allowed for clustering in the license. This LEF provision doesn't have any bearing on enabling total number or reload engines for distribution in the QlikView Distribution Service (QDS) settings in the QMC. As Marcus stated, the limiting factor on this setting is the total number of cores of the servers.
Are you clicking the Apply button after making the change? Can you provide screen captures or video of what occurs when you try to change this setting?
Best Regards
Thanks for your reply,
There is unfortunately no possibility to change this amount, the max Simultaneous engines is just a given number with no textbox or whatever.
The test environment has a CPU of 8 cores, the production environment has a CPU of 36 cores. So in my opinion this shouldn't limit our ability to change the max Simultaneous engines on the production environmnet.
Related to the reload-tasks you could set a much higher value for the number of engines as you have cores available. No error will occur. All parallel starting tasks which are above the core-number will be queued until they could be executed or they hit their timeout-setting or a similar setting and are terminated.
I would be quite surprised if this logic would be completely different by distribution tasks because these kind of settings are aimed to reduce the max. workload to balance the available resources between the various tasks and other QlikView services or further tools on the server respectively within the environment and of course the underlying OS.
Therefore I think it's more likely that anything is wrong within your installation and/or the configurations which ends in missing rights to change the settings.
It would be helpful if you shares some more information like the releases and installation-types of the environments, how were the configurations done (any copy & paste between the environments and/or from older installations), if it previously worked and not since a recent change of QlikView, OS, any security tool, whatever ... and further if it happens for other settings, too - in this case which one?
- Marcus
Hi,
This setting is stored in the C:\ProgramData\QlikTech\ManagementService\QVPR\DistributionService.xml.
Stop the QlikView Management Service, and make a Backup of DistributionService.xml.
Open the DistributionService.xml and go to the next to last line. Look for MaxSimultaneousQvb= and change the value there.
Restart the QlikView Management Service and see if the new value sticks
Bill
Hi @Bill_Britt,
Thanks for your reply, we have edited the DistributionService.xml file and rebooted the server. However the value unfortunately does not change (see the attachted screenshots).
In the DistributionService.xml there are two options to change the MaxSimultaneousQvb, we have tried multiple things with this file.
Situation 1,
We have replaced the MaxSimultaneousQvb on line 13 and line 45. This did not work.
Situation 2,
We have replaced the MaxSimultaneousQvb on line 45 but not on line 13 (as seen in the attached screenshot). This did not work.
Situation 3,
We have replaced the MaxSimultaneousQvb on line 13 but not on line 13. This did not work.
Also thank you for your reply @marcus_sommer,
Both the test environment and the production environment run on the latstest release of QlikView (v 12.70.20000.0), this is the only version QlikView has run on on this server. The installation of the production environment was not done with copying and pasting files, it was a clean and new installation on a clean server. As far as we can see the only affected setting by this issue is the Max number of simultaneous QlikView engines.
Thanks again everyone for your collaboration, it truly means a lot.