topic Re: Skipped Jobs - Accelerated Data Models in Reporting

Skipped Jobs - Accelerated Data Models

bill_king — Thu, 11 Feb 2021 17:41:04 GMT

Not sure where & how to address the below skipped job. I would appreciate any guidance

Report Name Skip Reason (Skip Count) Alert Actions

_ACCELERATE_DM_SA-IdentityManagement_Identity_Management.Expired_Identity_Activity_ACCELERATE_

The maximum number of concurrent historical scheduled searches on this instance has been reached (1)

none

Re: Skipped Jobs - Accelerated Data Models

richgalloway — Thu, 11 Feb 2021 14:27:01 GMT

The job name is in the format ACCELERATE_DM_<app name>_<datamodel name>_ACCELERATE.

Re: Skipped Jobs - Accelerated Data Models

bill_king — Thu, 11 Feb 2021 17:44:12 GMT

your response does not make sense to me on where & how to fix the issue.

Re: Skipped Jobs - Accelerated Data Models

scelikok — Thu, 11 Feb 2021 18:32:23 GMT

Hi @bill_king,

This error does not mean there is a problem on this report. You get this error, because your search head compute resources (CPU core count) is not enough for running concurrent search jobs.

- You can check your scheduled saved searches, alert, correlation search schedule times? Generally most of the scheduled jobs run every beginning hour. Because 5 min, 10 min, 15 min, 30 min, 60min schedules triggers at 00 minute every hour. You can try to change schedule times/periods.

- It is best to use Schedule window "auto" on schedule settings.

- If you CPU usage is not high you can tweak below settings on Search Head;

Server settings » Search preferences
Relative concurrency limit for scheduled searches --> 75
Relative concurrency limit for summarization searches --> 100