Enable idempontency for UserRefreshOverUserRangeWorker"
What does this MR do and why?
It enables idempotency for UserRefreshOverUserRangeWorker
Deduplication support for workers that uses load balancing was added in !69372 (merged), and this support is still under the feature flag (preserve_latest_wal_locations_for_idempotent_jobs
), we need to add a guard that will conditionally check if a worker is idempotent?
depending on the feature flag in case the worker utilizes load balancing capabilities.
This is just a safety measure, that in case we disable the mentioned feature flag, we don't end up reading stale data. It will be removed with feature flag rollout: #338350 (closed)
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
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.
Related to #341284 (closed)