Refactor Geo Event Worker and Service
What does this MR do and why?
This is a refactor:
- Fixes many Rubocop offenses
- Removes unused code
- The worker was already idempotent
- The change from
always
tosticky
data consistency is not a behavior change since it is not applicable to the Geo tracking DB. This worker only runs on secondary Geo sites and it will never write to the main or CI DB. Andsticky
waits for replication lag and switches to the primary if lag is too high.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Michael Kozono