You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/architecture/consensus/index.rst
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,16 +16,14 @@ CFT parameters can be configured when starting up a network (see :doc:`here </op
16
16
Extensions for Omission Faults
17
17
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18
18
19
-
.. warning:: Support for these extensions is work-in-progress. See https://github.com/microsoft/CCF/issues/2577.
20
-
21
19
The CFT consensus implementation in CCF also supports some extensions for :term:`omission fault`.
22
20
This may happen when the network is unreliable and may lead to one or more nodes being isolated from the rest of the network.
23
21
24
22
Supported extensions include:
25
23
26
24
- "CheckQuorum": the primary node automatically steps down, in the same view, if it does not hear back (via ``AppendEntriesResponse`` messages) from a majority of backups within a ``consensus.election_timeout`` period. This prevents an isolated primary node from still processing client write requests without being able to commit them.
27
-
- "NoTimeoutRetirement": a primary node that completes its retirement sends a ProposeRequestVote message to the most up-to-date node in the new configuration, causing that node to run for election without waiting for time out.
28
-
- A ProposeRequestVote message is also sent when a primary receives a termination signal. This reduces downtime when the orchestrator must suddenly retire the primary's host, but there is insufficient time to reconfigure the network first.
25
+
- "NoTimeoutRetirement": a primary node that completes its retirement sends a ``ProposeRequestVote`` message to the most up-to-date node in the new configuration, causing that node to run for election without waiting for time out.
26
+
- A ``ProposeRequestVote`` message is also sent when a primary receives a termination signal. This reduces downtime when the orchestrator must suddenly retire the primary's host, but there is insufficient time to reconfigure the network first.
29
27
- "PreVote": followers must first request a pre-vote before starting a new election. This prevents followers from starting elections (and increasing the term) when they are isolated from the rest of the network.
0 commit comments