<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distributed Systems on Mi&amp;Bee Blog</title><link>/en/tags/distributed-systems/</link><description>Recent content in Distributed Systems on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/distributed-systems/rss.xml" rel="self" type="application/rss+xml"/><item><title>From Hashmod to Jump Consistent Hash — stream-metrics-route Hash Algorithm Upgrade</title><link>/en/posts/telemetry/stream-metrics-three/</link><pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/telemetry/stream-metrics-three/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In &lt;a href="/en/posts/telemetry/stream-metrics-two/"&gt;the previous article&lt;/a&gt;, we reviewed the three-year evolution of stream-metrics-route and mentioned that the &amp;ldquo;dual hashmod scheduling&amp;rdquo; is the core scheduling mechanism of the entire gateway. However, during continuous production operation, one fatal flaw of hashmod became increasingly obvious—&lt;strong&gt;every scaling operation triggers full data redistribution&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This article documents the complete decision process of migrating from &lt;code&gt;hash % N&lt;/code&gt; (hashmod) to &lt;strong&gt;Jump Consistent Hash&lt;/strong&gt;: which candidate algorithms were evaluated, why Jump Hash was ultimately chosen, and the specific impact before and after migration.&lt;/p&gt;</description></item></channel></rss>