Differences

This shows you the differences between two versions of the page.

--- resolution_area:watchdog_resolutions:res-w9231 [2021/06/25 10:09] – external edit 127.0.0.1
+++ resolution_area:watchdog_resolutions:res-w9231 [2021/07/05 14:04] (current) – 10.91.120.28
@@ Line 1: / Line 1: @@
 =====SyncTasksTakingTooLong=====
-**Level:** Major
+**Level:** Major :!:
 **Purpose:**
+Checks if there are more than 10 sync jobs running for more than 12 hours.
 **Scenario:**
+Syncs jobs can take a long time and bottleneck other sync processes. The alarm checks the below query to see if there are more than 10 jobs taking longer than 12 hours.
+''SELECT COUNT(*) FROM general_discovery_sync_history gdsh WHERE started_by = "auto_scheduler" AND gdsh.start_date >= DATE_SUB(NOW(), INTERVAL 1 DAY) AND TIMESTAMPDIFF(HOUR, gdsh.start_date, gdsh.end_date) > 12;''
 **Resolution:**
+Check if there are too many sync jobs running at the same time. Alarm, config and performance can be the most demanding. If there are too many, the time can be changed. There is no need to have performance or config syncs running every hour.
 **Manual Action Steps:**
+Reconfigure sync times in the network_element_sync_schedule table
 **Auto Clear:**
+When the count drops below 10 for stuck syncs.

Internal Errigal Collaboration Wiki