It's obsolete anyway.

It's obsolete as we are not going to implement raft_applier fiber
anymore.

Use direct structure names instead of aliases
for better IDE code surfing

1

add roadmap-en

Tell a story.

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.

When bootstrapping an instance, there're two possible execution paths -
`start_boot` and `start_join`. While `start_join` takes all uuids from
JoinResponse, `start_boot` already deals with a bootstrapped `box.cfg`
(it's done in `start_discover`, refer to [1]). In order to make uuids
consistent across `box.cfg` and topology module, `start_boot` stage is
preceded with rebootstrap.

This case is also covered with a pytest.

- [1] doc/clustering.md

Alexander Tolstoy authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

Part of https://git.picodata.io/picodata/picodata/docs/-/issues/1