Commit dbad442b authored by Will Chandler's avatar Will Chandler Committed by Evan Read

Add common Praefect DB load to docs

There are two common reasons for the Praefect DB to experience high CPU
load, but currently we don't have these documented.
parent 08d4aa08
...@@ -435,6 +435,15 @@ Here are common errors and potential causes: ...@@ -435,6 +435,15 @@ Here are common errors and potential causes:
- Praefect cannot reach one or more of its child Gitaly nodes. Try running - Praefect cannot reach one or more of its child Gitaly nodes. Try running
the Praefect connection checker to diagnose. the Praefect connection checker to diagnose.
### Praefect database experiencing high CPU load
Some common reasons for the Praefect database to experience elevated CPU usage include:
- Prometheus metrics scrapes [running an expensive query](https://gitlab.com/gitlab-org/gitaly/-/issues/3796). If you have GitLab 14.2
or above, set `praefect['separate_database_metrics'] = true` in `gitlab.rb`.
- [Read distribution caching](praefect.md#reads-distribution-caching) is disabled, increasing the number of queries made to the
database when user traffic is high. Ensure read distribution caching is enabled.
### Determine primary Gitaly node ### Determine primary Gitaly node
To determine the primary node of a repository: To determine the primary node of a repository:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment