chore: enable backoff when event ordering is disabled #3121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Enabling backoff even when event ordering is disabled.
Additionally, increasing
jobIteratorMaxQueries
to 50 so that router can go deeper in jobsdb's queue in case a large number of events exist in the queue's head which are for the same userID and destination that is rate limited. By increasing the number of max queries we are effectively allowing the router to pickup jobs for other non-rate-limited users which are waiting at the tail of the queue.Notion Ticket
Link
Security