Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Client-streaming RPC backpressure is broken on Kestrel
See original GitHub issueRelated to #104. Demo code: https://github.com/Avilad/grpc-dotnet-flow-control-test.
When a client streams many small messages to a grpc-dotnet server, and the server consumes these messages slower than they are produced, WriteAsync() calls on the client are blocked as expected, but for each call the server makes to MoveNext(), WriteAsync() accepts more than one call before being blocked. This (presumably) causes a buildup of messages in Kestrel’s buffers, eventually leading to a “Request body too large” exception.
When the Grpc.Core server is used instead, the backpressure works as expected, and allows on average one WriteAsync() call for each MoveNext() call.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
FIXED
@Avilad seriously, great job at debugging/diagnosing this issue!