You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 25, 2020. It is now read-only.
New nodes joining an existing cluster add the complete membership list to the list of updates in its own Dissemination. These updates should already being propagated within the cluster and thus not needed in the dissemination of this node.
Since ringpop currently transfers the complete changes list on ping responses the network traffic created because of this increases with the number of nodes. This violates the claim made in section 2 of the SWIM paper where they claim the message size does not increase with the number of nodes in the cluster.
Suggested solution is to not use the membership list a new node receives upon joining as updates in the Dissemination protocol.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
New nodes joining an existing cluster add the complete membership list to the list of updates in its own Dissemination. These updates should already being propagated within the cluster and thus not needed in the dissemination of this node.
Since ringpop currently transfers the complete changes list on ping responses the network traffic created because of this increases with the number of nodes. This violates the claim made in section 2 of the SWIM paper where they claim the message size does not increase with the number of nodes in the cluster.
Suggested solution is to not use the membership list a new node receives upon joining as updates in the Dissemination protocol.
The text was updated successfully, but these errors were encountered: