fix(crawler): separate timeout per query #999
Merged
+3
−3
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
This aims to correctly apply intention of fix from #996 It did not work correctly because `context.WithTimeout` was created once per goroutine but was used for multiple queries within the `for p := range jobs` loop. This meant once the timeout expires for the first query, all subsequent queries in that worker would immediately fail since they're using the same expired context.
3 tasks
MarcoPolo
approved these changes
Nov 15, 2024
guillaumemichel
approved these changes
Nov 15, 2024
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.
This PR aims to correctly apply the fix from:
queryPeer#996 (cc @MarcoPolo @guillaumemichel @ligustah)Problem
It did not work as expected because
context.WithTimeoutwas created once per goroutine but was used for multiple queries within thefor p := range jobsloop.This meant once the timeout expires for the first query, all subsequent queries in that worker would immediately fail since they're using the same expired context. The crawl ended in ~15s instead of few minutes.
Fix is to have new context per job.