DT-937 - Remove nested threadpool #1852
Merged
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.
Jira ticket: https://broadworkbench.atlassian.net/browse/DT-937
Addresses
We were continuously running into instances where Azure snapshot create flights would get stuck. After adding some logging in previous PRs, we were able to pinpoint the issue.
For large requests, we are running out of threads in a nested, shared threadpool. The parent call would hand out all of the threads and then the nested call wouldn't have any more threads to hand out. It was stuck forever waiting for a new thread.
Summary of changes
Remove nested thread pool. Note: I expect that this means we'll see Azure Snapshot Create Jobs take longer.
Testing Strategy