diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-09 21:16:19 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-09 21:16:19 +0300 |
| commit | 1d4597596530af4e651048c14ab7e977cda38a2a (patch) | |
| tree | 5e7b1d12cac2f233319d2615b62fa6b0e3a93fbf /doc/development/sidekiq/idempotent_jobs.md | |
| parent | ad1604c833ff566409dea6acb27a6deff25713b8 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/sidekiq/idempotent_jobs.md')
| -rw-r--r-- | doc/development/sidekiq/idempotent_jobs.md | 24 |
1 files changed, 0 insertions, 24 deletions
diff --git a/doc/development/sidekiq/idempotent_jobs.md b/doc/development/sidekiq/idempotent_jobs.md index 40cdff7bb94..4b201e22ca9 100644 --- a/doc/development/sidekiq/idempotent_jobs.md +++ b/doc/development/sidekiq/idempotent_jobs.md @@ -185,30 +185,6 @@ end Duplicate jobs can happen when the TTL is reached, so make sure you lower this only for jobs that can tolerate some duplication. -## Deduplication with load balancing - -> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/6763) in GitLab 14.4. - -Jobs that declare either `:sticky` or `:delayed` data consistency -are eligible for database load-balancing. -In both cases, jobs are [scheduled in the future](#scheduling-jobs-in-the-future) with a short delay (1 second). -This minimizes the chance of replication lag after a write. - -If you really want to deduplicate jobs eligible for load balancing, -specify `including_scheduled: true` argument when defining deduplication strategy: - -```ruby -class DelayedIdempotentWorker - include ApplicationWorker - data_consistency :delayed - - deduplicate :until_executing, including_scheduled: true - idempotent! - - # ... -end -``` - ### Preserve the latest WAL location for idempotent jobs > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69372) in GitLab 14.3. |