Details
-
Type:
Epic
-
Status: Closed (View Workflow)
-
Priority:
Highest
-
Resolution: Done
-
Affects Version/s: v1.1.0
-
Component/s: fabric-orderer
-
Labels:
-
Epic Name:Raft Consensus (etcd/raft)
-
SDK Impact:No
-
Design Status:Reviewed
-
Function Test Status:Done
-
Documentation Status:Done
-
Sample/Tutorial:Done
-
Current Status:Delivered in v1.4.1. Kafka to raft migration completed in v1.4.2 and v2.0.
-
Test Plan:
-
Release Note:The ordering service now supports an additional consensus mechanism that uses the Raft protocol. Please refer to the documentation for configuration instructions.
Description
If this were titled as a story it would be:
As a Fabric ordering service operator/deployer, I wish to decrease my dependency on third-party binaries.
We propose to achieve this via an ordering service based on etcd/raft.
Raft still keeps us in CFT-land and as such, it is still not the optimal solution (BFT is, and that's also coming), but –
- It allows us to have an ordering service without Kafka/ZK depedencies, and
- It helps with the BFT development as well, since it gives us a chance to hook into Fabric a leader-based consensus protocol and carry those lessons over when writing the BFT plugin.
The design document goes over everything we'll need to do in order to make Raft a consensus option for Fabric. The spreadsheet goes over the rough plan of how we will be breaking this epic into stories. The last sheet on that spreadsheet includes a list of recommended resources and reference material.
