Notifications

596 views

Description

In New York release, if you note that there is a buildup of jobs in the sys_trigger table which are past the datetime in the next_action field and are not picked up for processing, you may be affected by this PRB. 

Some of the symptoms include:

  • a large number of jobs/records in sys_trigger table (>100,000)
  • a large number of jobs (more than 10,000) that are of the same name (such as ASYNC jobs) and having a lower priority (default priority is 100) and the next action datetime has past
  • there are a few long-running jobs on one or more nodes
  • there are available scheduler workers on various nodes and they looked to be idle (not processing jobs)

Steps to Reproduce

  1. Access <instance>.service-now.com/sys_trigger.do and filter for the following:
    • Next action at or before Today
    • State is Ready
    • Trigger type is not On Demand
  2. There will be a large number of records (>100,000). 
  3. Access <instance>.service-now.com/stats.do and review the "Background Scheduler" section, refresh a few times and note that there are available scheduler workers with "Current job: idle"
  •  
    •  

 

Workaround

As a workaround, please create a table index (composite) as follows:

Table: Schedule Item [sys_trigger]

Fields (Labels): Priority,Next action

Fields (name): priority,next_action


Related Problem: PRB1373305

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - Audit Management PA Content - Madrid 2019 Q1
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Policy and Compliance PA Content - Madrid 2019 Q1
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Risk Management PA Content - Madrid 2019 Q1
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - CMDB CI Class Models - 201909
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Check Point Integration - New York 2019 Q3
SR - SIR - CrowdStrike Intel Integration - Madrid 2019 Q1
SR - SIR - ElasticSearch Integration - Madrid 2019 Q1
SR - SIR - Exchange Online Integration - New York 2019 Q3 2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response Flow Designer Content - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Splunk Sighting Search Integration - Madrid 2019 Q1
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - SIR - Threat intelligence - New York 2019 Q3
SR - SIR - VirusTotal Integration - New York 2019 Q3
SR - SIR - WHOIS Integration - New York 2019 Q3
SR - VR - Configuration Compliance - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Fixed In

New York Patch 5
Orlando

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-07-02 14:34:32
Published:2020-03-24