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

Lack of backpressure #641

Closed
mrocklin opened this issue Nov 8, 2016 · 1 comment
Closed

Lack of backpressure #641

mrocklin opened this issue Nov 8, 2016 · 1 comment

Comments

@mrocklin
Copy link
Member

mrocklin commented Nov 8, 2016

It appears that we can get streams to lose data if we push a large amount of data without receiving. We can trigger this in the following test if we crank up the size of the sent data an order of magnitude:

distributed/tests/test_batched.py::test_sending_traffic_jam

I was able to reproduce this without the BatchedSend object, instead using standard distributed.core.read/write on normal Tornado streams.

This issue has only come up in stress testing, not in the wild, but is somewhat concerning.

@mrocklin
Copy link
Member Author

This was, I believe, resolved by #653

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant