Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
We have had this problem for years using different versions of QlikView Server.
It seems that if we have a reload job that runs every hour after running for a few days it just seems to lockup.
I am thinking of every day restarting the Distrubution Service. Any thoughts on this?
Thank You,
Michael
At a high level, in a single server environment, all of the QV services are vying for system resources. The QVS makes reservations in RAM via the Low/High Workingset values, default at 70%/90%. If these settings are default level then that leaves 30%/10% RAM for the other services, including QDS. Often times the symptoms you are describing can be attributed to resource constraints for QDS.
Suggest that you contact Qlik Support for assistance with this issue. Hope this helps.
Best Regards
Hi @mstoler,
Based upon your question, I assume that restarting the QDS typically resolves the issue. After restarting QDS, does this reload task typically run without issue for a while but then begin to experience performance issues? What type of QlikView environment do you have - single server environment with all QV services running on one Windows Server? Or a distributed environment with QV services distributed across two or more Windows Servers? When the issue begins to occur, what type of errors or warnings are you seeing in the task logs or QDS Root logs?
Best Regards
Hello,
Yes restarting QDS will always correct the issue.
This is only a problem on systems where we have hourly reloads. I have not seen this on systems with daily reloads.
This has been occurring for years on different versions. It seems to lockup when the qvw is being saved.
Thank You,
Michael
Okay. What type of QlikView environment do you have - single server environment with all QV services running on one Windows Server? Or a distributed environment with QV services distributed across two or more Windows Servers? When the issue begins to occur, what type of errors or warnings are you seeing in the task logs or QDS Root logs?
Best Regards
Hello,
Always just a single server. Today it locked up at 3:30 AM. Nobody was using the server at 3:30 AM today.
We don't see any errors. It just locks up when saving the qvw. And then that reload job does not run until we restart the QDS or Server.
Thanks,
Michael
At a high level, in a single server environment, all of the QV services are vying for system resources. The QVS makes reservations in RAM via the Low/High Workingset values, default at 70%/90%. If these settings are default level then that leaves 30%/10% RAM for the other services, including QDS. Often times the symptoms you are describing can be attributed to resource constraints for QDS.
Suggest that you contact Qlik Support for assistance with this issue. Hope this helps.
Best Regards