Differences

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

--- resolution_area:watchdog_resolutions:res-w9804 [2021/06/25 10:09] – external edit 127.0.0.1
+++ resolution_area:watchdog_resolutions:res-w9804 [2023/03/23 14:34] (current) – 10.91.110.100
@@ Line 1: / Line 1: @@
 =====mysqlLongQueryRunning=====
-**Level:** __Critical__
+**Level:** __Critical__ FIXME
 **Purpose:**
+To notify about long running queries which can negatively affect database performance. Some of these queries might not finish executing for days.
 **Scenario:**
+A query can be executed, usually by the user, which requires too many resources to process in a feasible amount of time. This also happens often for reports that use too wide of a date range, or in heavy reports that are usually scheduled.
 **Resolution:**
+This watchdog will resolve itself most of the time and it is important to let it resolve if it happens within a few hours. A resolution will occur when the process that exists for the extended period of time disappears.
 **Manual Action Steps:**
+Allow a few hours for the query to finish executing. If this does not happen:
+<code>show processlist;</code> - Look for the longest running query and investigate if the origin of the query, if it can be killed and if it needs changing.
+To kill the process (get the process id from the process list):
+<code>kill <insert processid here></code>
+For Amazon RDS (get the process id from the process list):
+<code>CALL mysql.rds_kill(<insert processid here>)</code>
 **Auto Clear:**
+Yes

Internal Errigal Collaboration Wiki