Allow small variance when running migration jobs
What does this MR do?
Related to #326840 (closed)
Allow the next batched background migration job to run if it is very close to the next allowed execution time. This check needs to be introduced since the sidekiq-cron process only polls for new jobs once per minute.
Due to small timing differences between sidekiq-cron and the tracking records for the migration, the next job is execution is often missed by a matter of seconds, resulting in it not running until the next minute.
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
Edited by Patrick Bair