Move fetcher feeding to separate goroutine to avoid deadlocking #3550
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.
EnumerateChildrenAsync
is sending slices of keys tofetchNodes
, but receives only one node per iteration, which, when coupled with recent addition of concurrency limit, can lead to deadlock whentoprocess
is full butnodes
is empty. This patch defers feedingtoprocess
to separate (unbounded) goroutines to allow concurrent IO between the two functions.Fixes #3505