Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Feb 19, 2024 7:32:57 AM
Feb 19, 2024 3:14:13 AM
After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed.
The Qlik Sense System_Repository log file will read:
"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes."
Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt
This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.
The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.
Take a backup of your environment before proceeding.
If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article.
Show base memory size of apps in QMC
QB-22795
QB-24301
Qlik Sense Enterprise on Windows May 2023, August 2023, November 2023, February 2024.
Hi @Filippo_Nicolussi_P ,
On a scenario with multiple servers and the Central server not being used for HUB nor Scheduled tasks, would this behavior be seen?
If this turns out to be true, the ideal scenario wouldn't be to disable the function, but to let it be populated by one of the other Engines that are serving the HUB or Scheduler services.
Thanks for sharing the steps.
meu ambiente on premises está configurado com multi nós, onde nó central, engine, proxy e scheduler estão separados.
Se esse ajuste fizer sentido para meu ambiente, você indicaria fazer em qual servidor?
abraços
@Filippo_Nicolussi_P @Sonja_Bauernfeind
We have the following recurrent error on all our nodes (System Repository):
"API call to Engine service was not successful: Failed to get app 'StaticByteSize'."
We are on May 2025 Patch2.
Is there a fix for this or is the recommendation still to disable the Base memory size ?
What is the practical impact of these errors on the system?
@Filippo_Nicolussi_P @Sonja_Bauernfeind any updates on the above?