-
Notifications
You must be signed in to change notification settings - Fork 107
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
in fullly connected mesh topolgy, topology update gossip's can get chatty #116
Comments
murali-reddy
added a commit
that referenced
this issue
Sep 18, 2019
updates then coalesce into a single update to gossip Fixes #116
bboreham
pushed a commit
that referenced
this issue
Sep 25, 2019
updates then coalesce into a single update to gossip Fixes #116
murali-reddy
added a commit
that referenced
this issue
Oct 2, 2019
broadcast to all peers address the issue #116
murali-reddy
added a commit
that referenced
this issue
Oct 3, 2019
broadcast to all peers address the issue #116
murali-reddy
added a commit
that referenced
this issue
Oct 24, 2019
broadcast to all peers address the issue #116
murali-reddy
added a commit
that referenced
this issue
Nov 1, 2019
broadcast to all peers address the issue #116
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On each connection add/delete/established event from a peer mesh router broadcasts topology updates to the peers. In fully connected topology broadcast would be to the all nodes in mesh.
A received topolgy gossip is further relayed to the peers if its a new update. While this should not be a concern in a stable topology it can be problematic in some use-cases.
For e.g.
Considering #114, #115 which resuts in high cpu usage, combination chatty topology gossip results in cascading effect.
As number of peers in the mesh increases it significantly impacts scalability.
Following metrics were gathered with instrumented mesh on 150 node kubernetes cluster running weave-net using mesh.
rx gossip broadcast
are received topology gossip per second.The text was updated successfully, but these errors were encountered: