User Tools

Site Tools


resolution_area:prometheus_resolutions:res-p1703

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
resolution_area:prometheus_resolutions:res-p1703 [2021/06/25 10:09] – external edit 127.0.0.1resolution_area:prometheus_resolutions:res-p1703 [2021/07/05 16:02] (current) wflaherty
Line 5: Line 5:
  
 **Purpose:** **Purpose:**
 +This alert is to ensure that the applications aren't doing to much with the Database at the same time. If a thread is slow or stuck in a running state then we must investigate.
  
 **Scenario:** More than 60% of MySQL connections have been in a running state on <server> for 5m. **Scenario:** More than 60% of MySQL connections have been in a running state on <server> for 5m.
  
 **Resolution:** **Resolution:**
 +Start investigating by connecting to the server and running the following query:
 +
 +<code>
 +SHOW PROCESSLIST;
 +</code>
 +
 +If there are many query that are trying to read from the database for the reporting manager or a search application then you may have to cancel some of these.
 +Generally, this isn't necessary unless there are other problems being caused because of this. If something was stuck, the you will likely be dealing with a long running query rather than pile of queries at once.
  
 **Manual Action Steps:** **Manual Action Steps:**
 +<code>
 +SHOW PROCESSLIST;
 +</code>
 +
 +If there is an application that is erroniously hammering the database with queries and requests then you may have to ask operations and the dev team about stopping the application. 
  
 **Auto Clear:** **Auto Clear:**
 +This will clear once less than 60% of the connections to the server are active
 +
resolution_area/prometheus_resolutions/res-p1703.1624612196.txt.gz · Last modified: 2021/06/25 10:09 by 127.0.0.1