chaoyoung commented on issue #12414: URL: https://github.com/apache/dubbo/issues/12414#issuecomment-6998866755
I retested this with the original `VoiceChat` proto after enabling both the Triple and Dubbo gRPC code generators in the sample. - On 3.1.11, the sample's Dubbo `grpc` client received replies before reporting `DEADLINE_EXCEEDED` at about 0.99 s with a 1 s timeout and 9.99 s with a 10 s timeout. The [generated stub](https://github.com/apache/dubbo/blob/dubbo-3.1.11/dubbo-compiler/src/main/resources/DubboGrpcStub.mustache#L105-L117) applies the timeout to the entire RPC. Receiving messages does not extend it. - With a 35 s deadline and the client calling `onCompleted()` after sending, all 200 concurrent streams completed with `OK` and returned all 22,400 expected replies. The same test with a standard grpc-java client passed against Triple on 3.1.10, 3.1.11, 3.2.20, and 3.3.7. For long-running streams, set the deadline to cover the expected session duration and half-close when the client is done sending. The retest is consistent with normal deadline behavior, so I'm closing this. Thanks to everyone who looked into it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
