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.
Http2ConnectionHandler#goAway should not initiate channel graceful shutdown
See original GitHub issueIntroduced by #9094, in Http2ConnectionHanlder, when there is no active stream, doing GO_AWAY with error code NO_ERROR will immediately shut down the channel once the GO_AWAY frame is sent. This breaks higher layer implementation’s logic of graceful shutdown, such as in gRPC. Now that the GOAWAY(<max id>), PING, PING(ACK), GOAWAY(<real id>) approach is left for higher layer implementations, graceful shutdown should not be initiated in Http2ConnectionHandler#goAway(...).
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (7 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
@voidzcy thanks a lot for verify the fix 😃
@normanmaurer I just pulled
4.1.37.Final-SNAPSHOT/ Fri Jun 07 21:05:54 UTC 2019to build gRPC and it succeeded.