This project intends to improve raft as the next-generation consensus protocol for distributed data storage systems (SQL, NoSQL, KV, Streaming, Graph ... or maybe something more exotic).
Currently, openraft is the consensus engine of meta-service cluster in databend.
drmingdrmer.main: network partition, process pause, process kill, slow packets, flaky packets, clock skew, membership churn, and all seven combined.OpenRaft's API continues to evolve. Upgrades before 1.0.0 may include incompatible changes. See the changelog. Commit messages start with a keyword indicating the type of change:
data-change: changes on-disk data types and may require a manual upgrade.change: introduces incompatible changes.feat: adds compatible, non-breaking features.fix: contains only bug fixes.| Branch | Status | Release | Upgrade guide |
|---|---|---|---|
main / release-0.10 |
Stable; active development | 0.10.0 | 0.9 โ 0.10 |
| release-0.9 | Bug fixes only | 0.9.26 (changelog) | 0.8 โ 0.9 |
release-0.8, release-0.7, and release-0.6 are closed; their upgrade guides remain available.
This benchmark measures the OpenRaft framework with minimal storage and networking; see benchmark details.
| Clients | Single writes (put/s) | Batch writes (4 entries/batch, put/s) |
|---|---|---|
| 4096 | 3,548,000 | 5,615,000 |
| 1024 | 3,006,000 | โ |
| 256 | 1,808,000 | โ |
| 64 | 912,000 | โ |
| 1 | 33,000 | โ |
single-threaded applications.See the full feature list.
Check out the CONTRIBUTING.md guide for more details on getting started with contributing to this project.
Thanks to everyone who contributes to OpenRaft:
OpenRaft is licensed under the terms of the MIT License or the Apache License 2.0, at your choosing.
OpenRaft originated from async-raft.