WIP: Follow-up: Improve retry mechanism for Sidekiq jobs with delayed data consistency
What does this MR do?
It introduces retry mechanism for replica with max_delayed_replica_retry_count
, and keep tracking job['delayed_retry_count'] separately from job['retry_count'].
This way we will retry if the replica is not up to date, and we will not decrease the retry count if the replica is not up to date.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #325519 (closed)
Edited by Nikola Milojevic