fix race condition when --parallel is used with a large number of dependent services #10544
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.
What I did
dependency graph traversal has been implemented with recursive calls, this prevent the error group max concurrency to be used as a parallel limit: a Node visitor, once completed, won't leave the routine concurrent slot for another use.
This PR changes the approach by introducing a "controller" routine, responsible to trigger visit of the adjacent nodes. Visitor notify abut completion by aa channel, doing so the routine can complete. This require limit to be set to concurrency + 1 for the controller. Controller exits after all nodes have been visited.
Related issue
fixes #10532
(not mandatory) A picture of a cute animal, if possible in relation to what you did