Set retry limit 2 for Zoekt::IndexerWorker
What does this MR do and why?
This matches up with what we do for ElasticCommitIndexerWorker and
this is a mitigation for
gitlab-com/gl-infra/production#8740 (comment 1360008460)
as we're seeing some projects with permanent indexing problems where
retries won't ever work. The constant retries are causing too much noise
in our logs and alerts.
Similar to ElasticCommitIndexerWorker it's also not critical if we run out of retries because the project will just indexed again the next time the repo is updated. It's all derived data so losing a job in this queue can always be recovered by just queueing again for the same project.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.