datafuselabs / openraft
- четверг, 6 января 2022 г. в 00:41:04
rust raft with improvements
Raft is not yet good enough. 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.
Get started: The guide is the best place to get started, followed by the docs for more in-depth details.
Openraft API is not stable yet. Before 1.0.0
, an upgrade may contain incompatible changes.
Check our change-log
Openraft is derived from async-raft with several bugs fixed:
threshold/2 < last_log_index - snapshot < threshold
; by drdr xp; 2021-07-08A full list of changes/fixes can be found in change-log
It is fully reactive and embraces the async ecosystem.
It is driven by actual Raft events taking place in the system as opposed to being driven by a tick
operation.
Batching of messages during replication is still used whenever possible for maximum throughput.
Storage and network integration is well defined via two traits RaftStorage
& RaftNetwork
.
This provides applications maximum flexibility in being able to choose their storage and networking mediums.
All interaction with the Raft node is well defined via a single public Raft
type, which is used to spawn the Raft async task, and to interact with that task.
The API for this system is clear and concise.
Log replication is fully pipelined and batched for optimal performance. Log replication also uses a congestion control mechanism to help keep nodes up-to-date as efficiently as possible.
It fully supports dynamic cluster membership changes with joint config.
The buggy single-step membership change algo is not considered.
See the dynamic membership
chapter in the guide.
Details on initial cluster formation, and how to effectively do so from an application's perspective, are discussed in the cluster formation chapter in the guide.
Automatic log compaction with snapshots, as well as snapshot streaming from the leader node to follower nodes is fully supported and configurable.
The entire code base is instrumented with tracing. This can be used for standard logging, or for distributed tracing, and the verbosity can be statically configured at compile time to completely remove all instrumentation below the configured level.
Check out the CONTRIBUTING.md guide for more details on getting started with contributing to this project.
Openraft is licensed under the terms of the MIT License or the Apache License 2.0, at your choosing.