Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UDP connection cause "stream reset" #507

Closed
NaNi-Z opened this issue Oct 11, 2023 · 1 comment
Closed

UDP connection cause "stream reset" #507

NaNi-Z opened this issue Oct 11, 2023 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@NaNi-Z
Copy link

NaNi-Z commented Oct 11, 2023

What happened:
UDP connection from edge to cloud will cause "stream reset", then UDP connection will not available again, only restart edgemesh on edge node will recover.

I1011 16:55:27.030478 1 proxysocket.go:180] "New UDP connection from client" address="x.x.x.x:50811"
I1011 16:55:27.030514 1 loadbalancer.go:618] "NextEndpoint for service" servicePortName="kube-system/kube-dns-edge:dns" address="x.x.x.x:50811" endpoints=[cloudnode1:coredns-548878875f-77cws:a.a.a.a:53 cloudnode1:coredns-548878875f-zt5v7:b.b.b.b:53]
I1011 16:55:27.030534 1 loadbalancer.go:679] "Mapped service to endpoint" service="kube-system/kube-dns-edge:dns" endpoint="cloudnode1:coredns-548878875f-77cws:b.b.b.b:53"
I1011 16:55:27.030628 1 tunnel.go:278] New stream between peer cloudnode1: {12D3KooWBr91n5RCjPuyxvscZjRDvYXpJQjkkNuDVm9B9BKrewNg: [/ip4/x.x.x.x/tcp/20006/p2p/12D3KooWBr91n5RCjPuyxvscZjRDvYXpJQjkkNuDVm9B9BKrewNg/p2p-circuit /ip4/x.x.x.x/tcp/20006/p2p/12D3KooWKLgcEsqdBpJaT1dcqvLqv8NDwVjkDJMRUBoALwf71CeJ/p2p-circuit /ip4/x.x.x.x/tcp/20006/p2p/12D3KooWDHKkUym46jSG2G5QKNrTpQioqRQeTDz4oiWxAQymi5yp/p2p-circuit /ip4/x.x.x.x/tcp/20006 /ip4/x.x.x.x/tcp/20006 /ip4/127.0.0.1/tcp/20006 /ip4/x.x.x.x/tcp/20006/p2p/12D3KooWDHKkUym46jSG2G5QKNrTpQioqRQeTDz4oiWxAQymi5yp/p2p-circuit /ip4/x.x.x.x/tcp/20006/p2p/12D3KooWBr91n5RCjPuyxvscZjRDvYXpJQjkkNuDVm9B9BKrewNg/p2p-circuit /ip4/x.x.x.x/tcp/20006/p2p/12D3KooWKLgcEsqdBpJaT1dcqvLqv8NDwVjkDJMRUBoALwf71CeJ/p2p-circuit]} success
E1011 16:55:27.031395 1 loadbalancer.go:686] "Dial failed" err="get proxy stream from cloudnode1 error: stream between paas241 reset err: stream reset"

What you expected to happen:
Do not "stream reset"

How to reproduce it (as minimally and precisely as possible):
expose a UDP service to edge, for example, coredns on cloud. Then run this on edge node.

for((i=0;;i++)); do echo $i; nslookup kubernetes.default.svc z.z.z.z; done

z.z.z.z is the ClusterIP of coredns service.
about 230 times you will see.

Anything else we need to know?:

Environment:

  • EdgeMesh version:1.13

  • Kubernetes version (use kubectl version):1.2.6

  • KubeEdge version(e.g. cloudcore --version and edgecore --version):1.13

  • Cloud nodes Environment:
    • Hardware configuration (e.g. lscpu):
    • OS (e.g. cat /etc/os-release):
    • Kernel (e.g. uname -a):
    • Go version (e.g. go version):
    • Others:
  • Edge nodes Environment:
    • edgecore version (e.g. edgecore --version):
    • Hardware configuration (e.g. lscpu):
    • OS (e.g. cat /etc/os-release):
    • Kernel (e.g. uname -a):
    • Go version (e.g. go version):
    • Others:
@NaNi-Z NaNi-Z added the kind/bug Categorizes issue or PR as related to a bug. label Oct 11, 2023
@Poorunga
Copy link
Member

Poorunga commented Oct 18, 2023

Traffic monitoring features have been merged: #506

It can help analyze UDP traffic for problems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants