So that’s why exists an option called polic圜heckFailOpen. reset reason: connection failureĪnd according to documentation when a request comes in, envoy asks Mixer if everything is good (authorization and other things), and if Mixer doesn’t reply, the request is not success. One thing we notice is that in service B, we get a lot of this error messages in the istio-proxy container: Mixer Report failed with: UNAVAILABLE:upstream connect error or disconnect/reset before headers. So we think it might be related with the sidecars. When this happens, we see the error log in service A throwing the “upstream connect error” message, but none in service B. So, this problem is happening randomly (it seems) and between different services.įor example we have a service A which needs to talk to service B, and some times we get this error, but after a while, the error goes away.
0 kommentar(er)
