diff options
| author | Greg Stark <stark@gitlab.com> | 2017-11-28 18:14:05 +0000 |
|---|---|---|
| committer | Greg Stark <stark@gitlab.com> | 2017-11-28 18:14:05 +0000 |
| commit | a35d6d3c479fa2259e6d32d207be99d980a711c6 (patch) | |
| tree | ae236d4cc5ae2c9f5b70a239c25a0f723c0daf17 | |
| parent | 7bab05b77041b40f8daf530744fc0c10b6c2330f (diff) | |
| download | gitlab-ce-be-wary-of-typos.tar.gz | |
I am certainly weary of debugging sidekiq but I don't think that's what was meantbe-wary-of-typos
| -rw-r--r-- | doc/administration/troubleshooting/sidekiq.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/troubleshooting/sidekiq.md b/doc/administration/troubleshooting/sidekiq.md index b71f8fabbc8..9d157720ad2 100644 --- a/doc/administration/troubleshooting/sidekiq.md +++ b/doc/administration/troubleshooting/sidekiq.md @@ -11,7 +11,7 @@ troubleshooting steps that will help you diagnose the bottleneck. debug steps with GitLab Support so the backtraces can be analyzed by our team. It may reveal a bug or necessary improvement in GitLab. -> **Note:** In any of the backtraces, be weary of suspecting cases where every +> **Note:** In any of the backtraces, be wary of suspecting cases where every thread appears to be waiting in the database, Redis, or waiting to acquire a mutex. This **may** mean there's contention in the database, for example, but look for one thread that is different than the rest. This other thread |