Improve handling and configuration of GenerateFederatedSearchIndex job #706
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the default queue was congested, the job would not be run within 1 hour. When the "fetch index" request came from another instance, it would attempt to generate the index synchronously because the index was not there in the cache. This failed because generating the index took longer than the 30 s request timeout. Now the job is dispatched 30 min before the requests should arrive. Also, the job can be pushed to a higher priority queue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If the default queue was congested, the job would not be run within 1 hour. When the "fetch index" request came from another instance, it would attempt to generate the index synchronously because the index was not there in the cache. This failed because generating the index took longer than the 30 s request timeout.
Now the job is dispatched 30 min before the requests should arrive. Also, the job can be pushed to a higher priority queue.