How Paxos Powers Zookeeper: A Simple Island Analogy Explained

Paxos Island Analogy

Zookeeper’s default FastLeaderElection algorithm is essentially a Paxos‑style leader election. The article describes Paxos with a simple island scenario where residents (Senators) decide on proposals.

There is an island with a fixed number of Senators.

Each proposal has a monotonically increasing identifier (PID).

A proposal is accepted only if a majority ((SenatorCount/2)+1) of Senators agree.

Senators only accept proposals with identifiers greater than the one they have recorded.

If a Senator receives a proposal with an identifier less than or equal to its current record, it rejects it, indicating the proposal has already been seen.

The goal is for all Senators to reach a consistent view of proposals.

Conflict Resolution Example

Three Senators (S1‑S3) simultaneously propose different values for the same proposal. S3 receives S1’s proposal first, records it, and rejects S2’s later proposal because its identifier is not higher, allowing S1’s proposal to become the accepted law.

S1 proposes setting the electricity price to 1 unit. S2 proposes setting it to 2 units. S3 processes S1’s proposal first, records it, and rejects S2’s because its identifier is not greater. S1’s proposal is accepted and becomes the official rule.

Mapping Paxos to Zookeeper

Island (Cluster) → ZKServerCluster

Senator → ZKServer

Proposal → ZNode change (Create/Delete/SetData…)

Proposal ID (PID) → Zxid (ZooKeeper Transaction ID)

Official law → All ZNodes and their data

While Paxos assumes equal participants, Zookeeper introduces a Leader, which also fits within the Paxos framework.

Leader (President) Role

Lamport’s “The Part‑Time Parliament” adds a President (Leader) who is the only one authorized to issue proposals; other servers forward their proposals to the President.

Operational Scenarios

Scenario 1: A client reads a ZNode; the server returns its local copy and may sync with the Leader for the latest data.

Scenario 2: A client requests a transaction (e.g., returning money); the server forwards the request to the Leader, which gathers consensus and updates the state.

Scenario 3: If the Leader fails, servers elect a new Leader, during which the service is temporarily unavailable.

These scenarios illustrate how Paxos concepts are realized in Zookeeper’s design, including session handling, watchers, and versioning, which merit further study.