<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>arbiter on BusyJay</title>
    <link>https://busyjay.com/tags/arbiter/</link>
    <description>Recent content in arbiter on BusyJay</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 04:00:00 +0800</lastBuildDate><atom:link href="https://busyjay.com/tags/arbiter/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Extending Raft algorithm: Witnesses and Arbiters, Part 2</title>
      <link>https://busyjay.com/post/witness-and-arbiter/</link>
      <pubDate>Sat, 19 Sep 2026 04:00:00 +0800</pubDate>
      
      <guid>https://busyjay.com/post/witness-and-arbiter/</guid>
      <description>The previous post described how to add a Learner role to the Raft consensus algorithm. This post discusses how to add the Witness and Arbiter roles.
The Witness and Arbiter concepts are very similar, yet they differ in subtle ways. Both are a kind of voter. A regular voter can both initiate elections and participate in log replication: as a leader it serves both read and write workloads, and as a follower it can still serve read-only workloads.</description>
    </item>
    
  </channel>
</rss>
