<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cluster on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/cluster/</link><description>Recent content in Cluster on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Tue, 07 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/cluster/rss.xml" rel="self" type="application/rss+xml"/><item><title>SWIM Protocol and Cluster Membership Management</title><link>https://blog.mickeyzzc.tech/en/posts/network/swim-membership-protocol/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/network/swim-membership-protocol/</guid><description>&lt;p&gt;In the previous article, we explored the core principles of the Gossip protocol in depth—Epidemic propagation models, the distinction between Anti-Entropy and Rumor-Mongering, and the mathematical foundation of the Phi Accrual failure detector. Gossip provides a general mechanism for information dissemination, but to build a complete distributed cluster, information dissemination alone is not enough: &lt;strong&gt;every node needs to know who else is in the cluster—who is online, who has left, and who has just joined.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>