High CPU usage and OOM error after upgrade to 15100
In some customer environments after upgrading to 15100, High CPU utilization and Out of Memory errors due to insufficient Heap space were seen.
1. High CPU utilization error (SD-132540 released in 15110 build)
In 15100 build version, we have introduced Zia Parser feature which is enabled by default in IT helpdesk portal and disabled in other available portals. For this feature, data training will occur during service startup for all portals (even when Zia parser is disabled). This is to try out "Test Zia Parser" option inside the Zia parser feature. However, in some big environments, training in available portals triggered High CPU usage.
This has been fixed in 15110 build - Training during service startup will occur only for Zia parser feature enabled portals. This training will occur only once and the trained data will be stored in a file. Post this, during every service startup, training will not occur due to this stored data file.
2. OOM error while initializing the Zia parser (SD-134060 which is to be released in 15250 build)
For customers in 15100 build, use the attached fjar file and execute the below queries and restart the service once.
For customers in 15110 - 15130 build, execute the below queries and restart the service once.
update ai_module set action_enabled=false where actionname='parser';
delete from Schedule where SCHEDULE_ID in (select s.SCHEDULE_ID from Schedule s inner join AI_Module am on am.ACTIONNAME = 'parser' where s.SCHEDULE_NAME like CONCAT('AITrainingSchedule', CAST(am.MODULEID AS VARCHAR)));
Customers migrating from 15100 to build version 15130 or above, Zia parser will be disabled in all portals. If customer enabled Zia parser post 15130 migration, use the above query to disable it and fix the OOM error.
For customers in 15140 build or above, execute the below queries to disable zia parser and parser training schedules and restart the service once to fix the OOM error.
update zia_module_prediction_mapping set enabled=false where predictionid in (select id from zia_predictions where internalname like 'parser');
DELETE FROM Schedule WHERE SCHEDULE_ID IN ( SELECT s.SCHEDULE_ID FROM Schedule s INNER JOIN zia_module_prediction_mapping zmpm ON s.SCHEDULE_NAME LIKE CONCAT('AITrainingSchedule', CAST(zmpm.id AS VARCHAR)) INNER JOIN zia_predictions zp ON zmpm.predictionid = zp.id WHERE zp.internalname = 'parser' );
New to ADSelfService Plus?
Related Articles
SQL Server High CPU - To collect queries consuming CPU resources
1. To get an idea of how much CPU the queries are currently using, out of overall CPU capacity, run the following statement: DECLARE @init_sum_cpu_time int, @utilizedCpuCount int --get CPU count used by SQL Server SELECT @utilizedCpuCount = COUNT( * ...High CPU Utilization during Backup
Cause: From 14740, below listed parameters will no longer be included in the command. As a result, when performing backups, 7-Zip utilizes a high number of CPU threads, leading to increased CPU usage. mmt - Sets number of CPU threads mmemuse - Sets a ...Error - Sanity Failed - Upgrade from 8121 to 11
While upgrading from 8121 to 11, after executing Updatemanager.bat and if the update fails, You need to check the Updatemanager logs in the path < Support Center Plus Application path -> Server-> Default-> Logs > . And if you find the below ...Error when Processing Request during Upgrade - Version8121 - 11
Error: While upgrading 8121 to 11011 when you get the below shown error, Cause of the error: The issue with the Upgrade is that the System defined user kept getting deleted and it was because of data anonymization. Solution : In 8121, Go to ...Upgrade Failed -> Reverting steps
This article covers 2 areas : a) Analysis stage b) Reversion steps (rollback) a) Analysis stage Please send the below files to our support for analysis: 1. Zip the complete log folder present under <servicedesk plus msp home>/server/default or from ...