Raft consensus algorithm
E467805
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.
All labels observed (3)
| Label | Occurrences |
|---|---|
| Raft consensus algorithm canonical | 4 |
| In Search of an Understandable Consensus Algorithm | 1 |
| Raft consensus protocol | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4765252 — 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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raft consensus algorithm Context triple: [Paxos consensus algorithm, influenced, Raft consensus algorithm]
-
A.
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.
-
B.
Paxos
Paxos is a small Greek island in the Ionian Sea, known for its clear turquoise waters, olive groves, and tranquil, less-touristed atmosphere.
-
C.
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.
-
D.
"Reaching Agreement in the Presence of Faults"
"Reaching Agreement in the Presence of Faults" is a seminal paper in distributed computing that introduced the Byzantine Generals Problem and laid the foundations for understanding consensus in unreliable, fault-prone systems.
-
E.
Byzantine Generals Problem
The Byzantine Generals Problem is a classic computer science and distributed systems thought experiment that illustrates the difficulty of achieving reliable consensus among participants in the presence of faulty or malicious actors.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Raft consensus algorithm Target entity description: 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.
-
A.
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.
-
B.
Paxos
Paxos is a small Greek island in the Ionian Sea, known for its clear turquoise waters, olive groves, and tranquil, less-touristed atmosphere.
-
C.
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.
-
D.
"Reaching Agreement in the Presence of Faults"
"Reaching Agreement in the Presence of Faults" is a seminal paper in distributed computing that introduced the Byzantine Generals Problem and laid the foundations for understanding consensus in unreliable, fault-prone systems.
-
E.
Byzantine Generals Problem
The Byzantine Generals Problem is a classic computer science and distributed systems thought experiment that illustrates the difficulty of achieving reliable consensus among participants in the presence of faulty or malicious actors.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
distributed consensus algorithm
ⓘ
fault-tolerant consensus protocol ⓘ |
| assumes |
non-Byzantine failures
ⓘ
reliable message delivery with retries ⓘ |
| designedBy |
Diego Ongaro
ⓘ
John Ousterhout ⓘ |
| ensures |
linearizability
ⓘ
strong consistency ⓘ |
| guarantees |
at most one leader per term
ⓘ
log entries are applied in order ⓘ no committed entry is lost ⓘ |
| hasGoal |
be more understandable than Paxos
ⓘ
provide equivalent fault-tolerant guarantees to Paxos ⓘ |
| hasOpenSourceImplementation |
HashiCorp Raft library
ⓘ
etcd/raft ⓘ
linked to:
etcd
|
| hasPhase |
leader election
ⓘ
log replication ⓘ membership changes ⓘ safety ⓘ |
| hasProperty |
deterministic behavior given same inputs
ⓘ
understandability emphasized over minimality ⓘ |
| hasWebsite | https://raft.github.io/ ⓘ |
| influenced | design of modern distributed databases ⓘ |
| introducedInPaper |
In Search of an Understandable Consensus Algorithm
ⓘ
linked to:
Raft consensus algorithm
|
| isComparedTo |
Paxos
ⓘ
linked to:
Paxos consensus algorithm
|
| operatesIn | asynchronous distributed systems ⓘ |
| provides | replicated state machine ⓘ |
| publicationYear | 2014 ⓘ |
| requires |
majority of nodes to be available
ⓘ
persistent storage for logs and terms ⓘ |
| supports |
cluster reconfiguration
ⓘ
joint consensus for membership changes ⓘ |
| tolerates | crash failures ⓘ |
| usedIn |
CockroachDB
ⓘ
Consul ⓘ LogCabin ⓘ RethinkDB ⓘ TiKV ⓘ etcd ⓘ |
| uses | leader-based replication ⓘ |
| usesConcept |
candidate
ⓘ
commit index ⓘ follower ⓘ leader ⓘ log index ⓘ term ⓘ |
| usesMechanism |
heartbeats
ⓘ
leader completeness property ⓘ log matching property ⓘ randomized election timeouts ⓘ |
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.
Instruction
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.
Input
Subject: Raft consensus algorithm Description of subject: 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.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.