habitat
habitat copied to clipboard
habitat-sh
SWIM: Membership update piggybacking limit
Per section 4.1 of the SWIM paper, membership update messages should be piggybacked on ping and ping-req messages at most λ.log n times.
This limit should be tracked globally, but the current implementation may be tracking it on a per-member basis, leading to over-piggybacking by a factor of n. This needs to be validated, and if so, corrected.
This may have performance implications for ram consumption as we plan for 1.0.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.