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

The module edgecontroller message channel is full #5557

Open
zhushuaifeifei opened this issue Apr 24, 2024 · 0 comments
Open

The module edgecontroller message channel is full #5557

zhushuaifeifei opened this issue Apr 24, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@zhushuaifeifei
Copy link

Environment

  • k8s master: v.1.21.5
  • cloudcore: v1.12.1
  • edgecore: v1.10.0

What happened

  • First, when edgenode disconnect, metamanager still update podstatus msg to cloud, and edged still update nodestatus msg to cloud, there msg were sent to edgehub, but were not consumed. Edgehub message channel will be full, and there are lots of goroutine would be created and halt when msg channel is full.
  • Second, when edgenode reconnect, lots of podstatus and nodestatus msg will be send to cloudhub immediately, all there msg would be send to edgecontroller, which will make edgecontroller message channel full. Other edge node nodestatus update msg can not be send to edgecontroller message channel in a few minutes, therefore other node will be mark notready.
  • Third, even if the node is online, POD still cannot be scheduled normally and always displays Pending. However, I checked on the edge node machine. Some have been scheduled and running, and some have not been scheduled. There are still nodes online and I manually stop them. The nodes are still online and have not been updated for dozens of minutes..

What you expected to happen

  • edgehub message channel not full when edge node disconnect
  • edgecontroller message channel not full when edge node reconnect
  • other edge node not be mark notready

How to reproduce it (as minimally and precisely as possible)

  • create 100+ pod to edge node
  • disconnect node for 30min
  • reconnect edge node

nodestatus and podstatus update msg will be overwrite when edge node disconnect.

@zhushuaifeifei zhushuaifeifei added the kind/bug Categorizes issue or PR as related to a bug. label Apr 24, 2024
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

1 participant