Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce IDeltaQueueWriter and a bit better tracking for connection issues #8120

Merged
merged 7 commits into from
Nov 10, 2021

Conversation

vladsud
Copy link
Contributor

@vladsud vladsud commented Nov 3, 2021

See #7312 for more details

@vladsud vladsud requested review from jatgarg and andre4i November 3, 2021 21:45
@github-actions github-actions bot added the area: loader Loader related issues label Nov 3, 2021
@vladsud
Copy link
Contributor Author

vladsud commented Nov 4, 2021

Note - for now I'm not going to merge this. I'm running it locally and occasionally can capture stacks, and they are pointing me in right direction. So it's possible I'll never merge it, though it might be useful for other things in the future.

…to TrackingInboundPauses

# Conflicts:
#	packages/loader/container-loader/src/deltaManager.ts
@vladsud
Copy link
Contributor Author

vladsud commented Nov 10, 2021

Note - I'll be abandoning this direction, as manual stress testing points to offender, and through careful refactoring I got to the point where it's easy to see and fix this issue - the last leg of this journey is PR #8206

But I'll reuse this PR to introduce IDeltaQueueWriter which might be useful for future

@vladsud vladsud changed the title Tracking who screws up pausing of inbound queues Introduce IDeltaQueueWriter and a bit better tracking for connection issues Nov 10, 2021
@vladsud vladsud merged commit 353e919 into microsoft:main Nov 10, 2021
@vladsud vladsud deleted the TrackingInboundPauses branch November 10, 2021 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: loader Loader related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants