diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-21 06:08:14 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-21 06:08:14 +0300 |
| commit | bc69b91579a1406bc62eb2ea696e5e35cff56d59 (patch) | |
| tree | 9f8158a8b7d09024c88b6dcd395ed7fc80621555 /doc/development/sidekiq/index.md | |
| parent | 6fbaac1974d2e9a0e5296a9da2d99f356a684f91 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/sidekiq/index.md')
| -rw-r--r-- | doc/development/sidekiq/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/sidekiq/index.md b/doc/development/sidekiq/index.md index d510414baa3..936388a14fe 100644 --- a/doc/development/sidekiq/index.md +++ b/doc/development/sidekiq/index.md @@ -121,7 +121,7 @@ Sidekiq workers are deferred by two ways, 1. Manual: Feature flags can be used to explicitly defer a particular worker, more details can be found [here](../feature_flags/index.md#deferring-sidekiq-jobs). 1. Automatic: Similar to the [throttling mechanism](../database/batched_background_migrations.md#throttling-batched-migrations) in batched migrations, database health indicators are used to defer a Sidekiq worker. - To use the automatic deferring mechanism, worker has to opt-in by calling `defer_on_database_health_signal` with gitlab_schema, delay_by (time to delay) and tables (which is used by autovacuum db indicator) as it's parameters. + To use the automatic deferring mechanism, worker has to opt-in by calling `defer_on_database_health_signal` with `gitlab_schema`, delay_by (time to delay) and tables (which is used by autovacuum db indicator) as it's parameters. **Example:** |