Closed cobb-tx closed 2 years ago
I don't really understand what is wrong exactly (Envoy doesn't close a connection when the peer resets it?) and where Envoy is sitting in this setup.
Perhaps @alyssawilk @lizan could help.
if Envoy is setting up for a connection close and not sending a FIN could it be because of the delay close? have you tried turning that delay down and seeing if it helps?
@rojkov sorry I describe is not very clear. the peer resets it, probably because the envoy (istio-ingress)close connection without FIN I guess。 and This is by intermittent
@alyssawilk i will try it. I tried before timeout and keeplive but It's not working
i will close this issue because this bug not envoy,it is kube-proxy problem and i will The process of troubleshooting a problem in next
i find this can fix this bug but incomplete because There will be more 502
ipvsadm --set 7500 120 300
and we consider k8s-ingress(nginx) keeplive 75s There's reason No 502, i will test envoy timeout 75s
I'll send issue in istio https://github.com/istio/istio/issues/37608
Bug Description
istio ingress Intermittent unavailable,nginx ingress available
it seems envoy close TCP wihtout send FIN pack。
Flow Path: kong ——》istio-ingress——》sidecar——》service
I recorded the istio-ingress debug log and i think is ok
but kong log error like this (Please ignore the time difference) access.log upstream_status=[502, 200]
error.log
and I use tcpdump
what can i do to fix this bug?
Version
Additional Information
No response