Reduce delay for expired removal from ES
What does this MR do and why?
The subscription expiration detection/removal from Elasticsearch was updated in !143395 (merged)
The worker schedule delay of 12 hours is too long and caused a race condition where the following happened:
- subscription expired
- cron worker ran and scheduled a future removal worker
- subscription was renewed
- future removal worker ran
slack thread (internal) support ticket (internal)
This MR reduces the delay to 5 minutes to reduce the chance for a race condition to a smaller window
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.
Screenshots or screen recordings
Backend change only
How to set up and validate locally
The only change is the delay value so I recommend validating with CI
Edited by Terri Chu