Zab protocol
E705296
The Zab protocol is a crash-recovery atomic broadcast and consensus algorithm used by Apache ZooKeeper to ensure ordered, reliable updates across distributed nodes.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Zab protocol canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7985810 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Zab protocol Context triple: [Apache ZooKeeper, consensusAlgorithm, Zab protocol]
-
A.
Paxos
Paxos is a small Greek island in the Ionian Sea, known for its clear turquoise waters, olive groves, and tranquil, less-touristed atmosphere.
-
B.
Paxos consensus algorithm
The Paxos consensus algorithm is a fault-tolerant protocol for achieving agreement among distributed systems, widely used as a foundation for reliable, replicated state machines and modern distributed databases.
-
C.
Raft consensus algorithm
Raft consensus algorithm is a distributed consensus protocol designed to be more understandable and easier to implement than Paxos while providing equivalent fault-tolerant guarantees.
-
D.
Algorand blockchain protocol
Algorand blockchain protocol is a scalable, secure, and energy-efficient public blockchain platform designed by cryptographer Silvio Micali that uses a pure proof-of-stake consensus mechanism.
-
E.
Practical Byzantine Fault Tolerance
Practical Byzantine Fault Tolerance is a consensus algorithm for distributed systems that efficiently tolerates Byzantine (arbitrary) faults, enabling reliable operation even when some nodes behave maliciously or unpredictably.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Zab protocol Target entity description: The Zab protocol is a crash-recovery atomic broadcast and consensus algorithm used by Apache ZooKeeper to ensure ordered, reliable updates across distributed nodes.
-
A.
Paxos
Paxos is a small Greek island in the Ionian Sea, known for its clear turquoise waters, olive groves, and tranquil, less-touristed atmosphere.
-
B.
Paxos consensus algorithm
The Paxos consensus algorithm is a fault-tolerant protocol for achieving agreement among distributed systems, widely used as a foundation for reliable, replicated state machines and modern distributed databases.
-
C.
Raft consensus algorithm
Raft consensus algorithm is a distributed consensus protocol designed to be more understandable and easier to implement than Paxos while providing equivalent fault-tolerant guarantees.
-
D.
Algorand blockchain protocol
Algorand blockchain protocol is a scalable, secure, and energy-efficient public blockchain platform designed by cryptographer Silvio Micali that uses a pure proof-of-stake consensus mechanism.
-
E.
Practical Byzantine Fault Tolerance
Practical Byzantine Fault Tolerance is a consensus algorithm for distributed systems that efficiently tolerates Byzantine (arbitrary) faults, enabling reliable operation even when some nodes behave maliciously or unpredictably.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
atomic broadcast protocol
ⓘ
consensus algorithm ⓘ crash-recovery protocol ⓘ |
| assumes |
non-Byzantine failures
ⓘ
reliable communication channels ⓘ |
| designedFor |
distributed systems
ⓘ
replicated state machines ⓘ |
| ensures |
committed transactions survive leader changes
ⓘ
followers apply transactions in the same order as leader ⓘ only one active leader at a time ⓘ |
| ensuresProperty |
atomic broadcast
ⓘ
durable updates ⓘ ordered updates ⓘ reliable broadcast ⓘ total order broadcast ⓘ |
| fullName | ZooKeeper Atomic Broadcast protocol NERFINISHED ⓘ |
| guarantees |
agreement among non-faulty nodes
ⓘ
liveness under partial failures ⓘ no data loss for committed transactions ⓘ prefix ordering of committed transactions ⓘ |
| handles |
follower crash recovery
ⓘ
leader crash recovery ⓘ |
| hasAbbreviation | Zab NERFINISHED ⓘ |
| hasPhase |
broadcast phase
ⓘ
discovery phase ⓘ leader election phase ⓘ synchronization phase ⓘ |
| hasProperty |
leader-based atomic broadcast
ⓘ
log-based state replication ⓘ primary-backup style replication ⓘ |
| implementedIn | Apache ZooKeeper server codebase ⓘ |
| inspiredBy | Viewstamped Replication NERFINISHED ⓘ |
| maintains | global order of ZooKeeper transactions ⓘ |
| publication | “Zab: High-performance broadcast for primary-backup systems” NERFINISHED ⓘ |
| relatedTo |
Paxos
NERFINISHED
ⓘ
Raft consensus algorithm NERFINISHED ⓘ |
| requires | distinguished leader ⓘ |
| supportsModel | crash-recovery failure model ⓘ |
| usedBy |
Apache Hadoop ecosystem components via ZooKeeper
ⓘ
Apache ZooKeeper NERFINISHED ⓘ |
| usedFor |
coordination in distributed applications
ⓘ
leader-based replication ⓘ replicated log management ⓘ |
| usedIn |
ZooKeeper quorum-based write operations
ⓘ
ZooKeeper transaction ordering ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Zab protocol Description of subject: The Zab protocol is a crash-recovery atomic broadcast and consensus algorithm used by Apache ZooKeeper to ensure ordered, reliable updates across distributed nodes.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.