diff options
| author | Alex Jordan <alex@strugee.net> | 2015-11-16 02:01:26 -0800 |
|---|---|---|
| committer | Alex Jordan <alex@strugee.net> | 2015-11-16 16:50:05 -0800 |
| commit | 3300db70ff53699732672824859186cd083623fa (patch) | |
| tree | 98a8e79a3887ad710c8f09651ad5dc62e2598dcc /doc/operations | |
| parent | 3777b233a35509c4ed13e145624370884468cbc2 (diff) | |
| download | gitlab-ce-3300db70ff53699732672824859186cd083623fa.tar.gz | |
Rewrite HTTP links to force TLS, where possible
Diffstat (limited to 'doc/operations')
| -rw-r--r-- | doc/operations/unicorn.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/operations/unicorn.md b/doc/operations/unicorn.md index 3998da01f01..bad61151bda 100644 --- a/doc/operations/unicorn.md +++ b/doc/operations/unicorn.md @@ -52,7 +52,7 @@ leak memory, probably because it does not handle user requests.) To make these memory leaks manageable, GitLab comes with the [unicorn-worker-killer gem](https://github.com/kzk/unicorn-worker-killer). This -gem [monkey-patches](http://en.wikipedia.org/wiki/Monkey_patch) the Unicorn +gem [monkey-patches](https://en.wikipedia.org/wiki/Monkey_patch) the Unicorn workers to do a memory self-check after every 16 requests. If the memory of the Unicorn worker exceeds a pre-set limit then the worker process exits. The Unicorn master then automatically replaces the worker process. @@ -83,4 +83,4 @@ is a normal value for our current GitLab.com setup and traffic. The high frequency of Unicorn memory restarts on some GitLab sites can be a source of confusion for administrators. Usually they are a [red -herring](http://en.wikipedia.org/wiki/Red_herring). +herring](https://en.wikipedia.org/wiki/Red_herring). |