Empty reply from server request svc by gateway
What happened:
Empty reply from server request svc by gateway

What you expected to happen: except normal response How to reproduce it (as minimally and precisely as possible): just retry N times Anything else we need to know?:
Environment:
-
EdgeMesh version: v1.12
-
Kubernetes version (use
kubectl version): v1.23.8 -
KubeEdge version(e.g.
cloudcore --versionandedgecore --version): v1.11.1 -
Cloud nodes Environment:
- Hardware configuration (e.g.
lscpu): 4C 8G - OS (e.g.
cat /etc/os-release): centos7 - Kernel (e.g.
uname -a): Linux k8s-master 3.10.0-1160.66.1.el7.x86_64 #1 SMP Wed May 18 16:02:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux - Go version (e.g.
go version): NA - Others:
- Hardware configuration (e.g.
-
Edge nodes Environment:
- edgecore version (e.g.
edgecore --version): v1.11.1 - Hardware configuration (e.g.
lscpu): 4C 8G - OS (e.g.
cat /etc/os-release): centos7 - Kernel (e.g.
uname -a): Linux k8s-edge01 3.10.0-1160.66.1.el7.x86_64 #1 SMP Wed May 18 16:02:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux - Go version (e.g.
go version):NA - Others:
- edgecore version (e.g.
Can you show some edgemesh logs? When "Empty reply from server" occurs
Can you show some edgemesh logs? When "Empty reply from server" occurs
E1011 08:26:58.971158 1 loadbalancer.go:683] "Dial failed" err="dial tcp 172.17.0.3:80: connect: connection refused" E1011 08:26:59.972033 1 loadbalancer.go:683] "Dial failed" err="get proxy stream from default-edge-node error: new stream between default-edge-node err: failed to find any peer in table" E1011 08:27:01.973063 1 loadbalancer.go:683] "Dial failed" err="get proxy stream from default-edge-node error: new stream between default-edge-node err: failed to find any peer in table" E1011 08:27:01.973278 1 protocol.go:160] "Failed to connect to balancer" err="failed to connect to an endpoint" E1011 08:27:01.973731 1 protocol.go:48] read http request err: read tcp 192.168.22.224:23333->192.168.22.224:38260: use of closed network connection E1011 08:27:01.973886 1 protocol.go:51] close conn err: close tcp 192.168.22.224:23333->192.168.22.224:38260: use of closed network connection
You need deploy edgemesh-agent to node default-edge-node
You need deploy edgemesh-agent to node default-edge-node
I deployed two services ,while I deploy two VirtualService what have the same domain but different route path,get the result

while I deploy a VirtualService what has two different route path ,get the result
