diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-06 06:08:08 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-06 06:08:08 +0300 |
| commit | a6011c3d70e0e8ac318ba6629183c44f8614c4df (patch) | |
| tree | a3d21394d63c47448998c89f01eb88e57c0ed8ce /doc/development/chaos_endpoints.md | |
| parent | ffc757a7a92535559c20eb706593f7358d9bf589 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/chaos_endpoints.md')
| -rw-r--r-- | doc/development/chaos_endpoints.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/development/chaos_endpoints.md b/doc/development/chaos_endpoints.md index 2e55f19cd91..26ff3d2def7 100644 --- a/doc/development/chaos_endpoints.md +++ b/doc/development/chaos_endpoints.md @@ -47,7 +47,7 @@ To simulate a memory leak in your application, use the `/-/chaos/leakmem` endpoi NOTE: **Note:** The memory is not retained after the request finishes. Once the request has completed, the Ruby garbage collector will attempt to recover the memory. -``` +```plaintext GET /-/chaos/leakmem GET /-/chaos/leakmem?memory_mb=1024 GET /-/chaos/leakmem?memory_mb=1024&duration_s=50 @@ -72,7 +72,7 @@ This endpoint attempts to fully utilise a single core, at 100%, for the given pe Depending on your rack server setup, your request may timeout after a predetermined period (normally 60 seconds). If you're using Unicorn, this is done by killing the worker process. -``` +```plaintext GET /-/chaos/cpu_spin GET /-/chaos/cpu_spin?duration_s=50 GET /-/chaos/cpu_spin?duration_s=50&async=true @@ -96,7 +96,7 @@ This endpoint can be used to model yielding execution to another threads when ru Depending on your rack server setup, your request may timeout after a predetermined period (normally 60 seconds). If you're using Unicorn, this is done by killing the worker process. -``` +```plaintext GET /-/chaos/db_spin GET /-/chaos/db_spin?duration_s=50 GET /-/chaos/db_spin?duration_s=50&async=true @@ -119,7 +119,7 @@ This endpoint is similar to the CPU Spin endpoint but simulates off-processor ac As with the CPU Spin endpoint, this may lead to your request timing out if duration_s exceeds the configured limit. -``` +```plaintext GET /-/chaos/sleep GET /-/chaos/sleep?duration_s=50 GET /-/chaos/sleep?duration_s=50&async=true @@ -142,7 +142,7 @@ This endpoint will simulate the unexpected death of a worker process using a `ki NOTE: **Note:** Since this endpoint uses the `KILL` signal, the worker is not given a chance to cleanup or shutdown. -``` +```plaintext GET /-/chaos/kill GET /-/chaos/kill?async=true ``` |