CAICAIIs commented on issue #12414:
URL: https://github.com/apache/dubbo/issues/12414#issuecomment-3122039989
I cloned the repository provided by the issue reporter and tried to
reproduce the problem. Here are my findings:
Test Results:
1. Triple server with Triple client: works normally, bidirectional
streaming is successful.
2. gRPC server with gRPC client: works normally, bidirectional
streaming is successful.
3. Triple server with gRPC client: after about 10 seconds, the client
receives a DEADLINE_EXCEEDED error.
Analysis:
This issue is caused by a lack of compatibility between the Dubbo Triple
protocol and the gRPC protocol in bidirectional streaming mode. Although both
protocols are based on HTTP/2, there are differences in their implementations,
which leads to communication failures and timeouts when they are mixed.
Conclusion and Suggestion:
To avoid this problem, it is recommended to use the same protocol for both
the server and the client—either both use Triple, or both use gRPC. Mixing the
two protocols is not supported for bidirectional streaming scenarios.
Additionally, I noticed that when the protocols are mixed, some data may be
exchanged at first, but the connection will eventually time out due to protocol
differences. This explains why partial communication may appear to succeed
before the error occurs.
--
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]
