Georgy Moshkin authored 2 years ago and Georgy Moshkin committed 2 years ago

Some users may change their "target-dir" cargo setting for example to
make it shared between all projects (may speed up some builds).
It that case our integration tests should be looking for the executable
in the right place.

It's already called `raft_conf_change_loop` in code.

Extend documentation with raft log processing algorithm.

Describe `conf_change_loop` and graceful shutdown logic.

Bring the algorithm description in accordance with actual
implementation. Also provide some comments to the code.

Everywhere in code use `RaftId`, `RaftTerm`, `RaftIndex` instead of
obscure `u64`.

Georgy Moshkin authored 2 years ago and Georgy Moshkin committed 2 years ago

It prints the raft log in a concise and readable way