Replies: 2 comments 1 reply
-
|
Hello. Have you found a solution ? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I did not, unfortunately. |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried tonic-web? Server::builder()
.accept_http1(true)
.add_service(
tonic_web::enable(
GreeterServer::new(greeter)
)
)
.serve(addr)
.await?;there is also an example: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign
EA2C
in to comment
-
Hello,
We are running some grpc clients and servers in a Kubernetes environment. Every server sits behind and nginx ingress controller that is able to route HTTP/2 traffic to a set of pods. We are able to connect to our grpc servers from a our grpc clients using the Kubernetes ingress under regular operation.
We are seeing an occasional issue when the server pods get rotated where nginx might temporarily return
502 Bad Gatewayand we see an error on the client like this:After looking at the code and the other open and closed issues, my understanding is that nginx is returning a HTTP/1 response and that is not handled correctly by the tonic grpc client, which behind the scenes uses hyper configured to only handle HTTP/2 responses. Please correct me if I am wrong with any of these assumptions.
If that is the case, what are options do we have to make it work consistently? Is there any setting we can change to make the tonic client understand the HTTP/1 errors and keep retrying until service is back in place? Looking for general guidance.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions