Aucune description

Jing Yang fb2285aa53 Update dependency crossbeam-utils to the newest version. il y a 5 ans
src 2a3d79a1c3 Update a few comments so that they are more relevant. il y a 5 ans
tests 1ba448e33f Remove DropGuard and use scopeguard. il y a 5 ans
.gitignore c5649d974f Ignore project files. il y a 5 ans
Cargo.toml fb2285aa53 Update dependency crossbeam-utils to the newest version. il y a 5 ans
MIT-LICENSE f374ec7dce Add license file, update toml. il y a 5 ans
README.md 12b2c96aea Update readme. il y a 5 ans
rustfmt.toml 3c80c4ae2b Implement the RPC layer. il y a 5 ans

README.md

Ruaft: Raft implemented in Rust

Ruaft is a Rust version of the Raft consensus protocol. The name is clearly made up.

At the moment it is a gigantic class lives in a single file. It exposes 4 APIs, to create a Raft instance (new()), start a new contract (start()), get the current status (get_status()) and shut it down (kill()). When a consensus is reached, it notifies the clients via an apply_command callback. It saves its internal state to local disk via a persister, which is supplied at creation.

There are also two half-APIs: process_append_entries() and process_request_vote(), serving requests from other Raft instances of the same setup.

Testing

The implementation is thoroughly tested. I copied (and translated) the tests from an obvious source. To avoid being indexed by a search engine, I will not name the source. The testing framework from the same source is also translated from the original Go version. The code can be found at labrpc repo.

Running

It is close to impossible to run ruaft outside of the testing setup under tests. One would have to supply an RPC environment plus bridges, a persister and an apply_command callback.

Things would improve after I implement an RPC interface and improve the persister trait.

Next steps

  • Split into multiple files
  • Add public documentation
  • Add a proper RPC interface to all public methods
  • Benchmarks
  • Allow storing of arbitrary information, instead of a i32.