Expand description
Raft consensus implementation for ruvector distributed metadata
This crate provides a production-ready Raft consensus implementation following the Raft paper specification for managing distributed metadata in the ruvector vector database.
Re-exports§
pub use node::RaftNode;pub use node::RaftNodeConfig;pub use rpc::AppendEntriesRequest;pub use rpc::AppendEntriesResponse;pub use rpc::InstallSnapshotRequest;pub use rpc::InstallSnapshotResponse;pub use rpc::RequestVoteRequest;pub use rpc::RequestVoteResponse;pub use state::LeaderState;pub use state::PersistentState;pub use state::RaftState;pub use state::VolatileState;
Modules§
- election
- Leader election implementation
- log
- Raft log implementation
- node
- Raft node implementation
- rpc
- Raft RPC messages
- state
- Raft state management
Enums§
- Raft
Error - Errors that can occur during Raft operations
Type Aliases§
- LogIndex
- Log index in Raft log
- NodeId
- Node identifier type
- Raft
Result - Result type for Raft operations
- Term
- Term number in Raft consensus