You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't really know if here is the right place to ask, but I'll try anyway. For the sake of clarity, I've asked the same on Envoy GitHub as I don't really know where the problem lies: envoyproxy/envoy#16811
A bit of context
We've an Istio 1.8.3 installation on a 1.18.x Kubernetes clusters. There are two pods (let's say ORIGIN and DEST) where ORIGIN is making a gRPC call to DEST, through a Kubernetes service that is proxying the DEST pod.
The situation is this:
We are using higherkindness/mu-scala
without Istio sidecars (i.e. Envoy proxies) all is going well.
With the sidecars the gRPC communication is not working, we receive an error like Received unexpected EOS on empty DATA frame from server.
Here are the logs, one for successful communication (without sidecars) and one for bad communication (with sidecars)
Hi everyone,
I don't really know if here is the right place to ask, but I'll try anyway. For the sake of clarity, I've asked the same on Envoy GitHub as I don't really know where the problem lies: envoyproxy/envoy#16811
A bit of context
We've an Istio 1.8.3 installation on a 1.18.x Kubernetes clusters. There are two pods (let's say
ORIGIN
andDEST
) whereORIGIN
is making a gRPC call toDEST
, through a Kubernetes service that is proxying theDEST
pod.The situation is this:
Received unexpected EOS on empty DATA frame from server
.Here are the logs, one for successful communication (without sidecars) and one for bad communication (with sidecars)
Successful communications logs
Bad Communication logs
Differences in logs
Unfortunately I'm no expert in debugging gGPC services, and There's one thing that i clearly see:
INBOUND DATA
log line:INBOUND DATA
log lines:and the last one has
length=0
bytes, so I suppose that this is giving theReceived unexpected EOS on empty DATA frame from server
errorEnvoy logs
Just to add an important info, here are the Envoy proxies logs for above communication
ORIGIN pod
DEST pod
Hope that this is enough to let someone of you understand what my problem is.
Thanks
The text was updated successfully, but these errors were encountered: