An error occurred while fetching the assigned milestone of the selected merge_request.
Huge amount of RowExclusiveLocks alert
1 unresolved thread
1 unresolved thread
@pcarranza @yorickpeterse @ahanselka there is no runbook and proper description for this alert. Feel free to add proper texts.
It is alert from the issue - https://gitlab.com/gitlab-com/infrastructure/issues/1135
Edited by Seth Itschner
Merge request reports
Activity
mentioned in issue infrastructure#1135
- alerts/gitlab-db-locks.rules 0 → 100644
1 ## DB lock alerts 2 ALERT PostgresTooManyRowExclusiveLocks 3 IF sum(pg_locks_count{mode="rowexclusivelock"}) > 100 4 FOR 30m 5 LABELS {severity="critical"} 6 ANNOTATIONS { 7 title="Too many row exclusive locks: {{ $value }}", 8 description="Huge amount of row exclusive locks can result in GitLab.com inavailability. Check http://performance.gitlab.net/dashboard/db/postgres-stats.", I would use:
Huge amounts of ROW EXCLUSIVE locks (used by SQL UPDATEs for example) can result in GitLab.com being unresponsive. See http://performance.gitlab.net/dashboard/db/postgres-stats for more information.
Edited by yorickpeterse-stagingchanged this line in version 3 of the diff
assigned to @sitschner
added 176 commits
-
a2ba5a72...dc44c56b - 175 commits from branch
master - 79d44e50 - Huge amount of RowExclusiveLocks alert
-
a2ba5a72...dc44c56b - 175 commits from branch
Please register or sign in to reply