Harald Ng

How to handle committed ConfChangeV2

2

Is it possible to provide an example on how to handle a committed ConfChangeV2 Entry? The example in `single_mem_node` is still a TODO and in `five_mem_node` still uses the old...

Unexpected FinalizeMembershipChange entries in commited entries after finalize

2

I assume from the documentation that `begin_membership_change` should be called once by the leader and `finalize_membership_change` should be called once by all nodes. Please let me know if that is...

In-memory storage for benchmarking

4

Hello, I'm master student doing my thesis where I investigate in performance of distributed consensus algorithms. In the documentation it says that the in-memory storage cannot be bootstrapped. Is there...

By using snapshots in the prepare phase (#38), entries or a snapshot of a server that was previously decided might be overwritten by the `AcceptSync`. However, we cannot determine what...

`omnipaxos_runtime` was initially designed for users to just have something that works out of the box. We can replace this by doing a proper example instead with tokio in `omnipaxos_core/examples`....

Let user define an interval of min and max for heartbeat timeout. BLE can then adaptively learn an appropriate timeout e.g. average of last 10 rounds etc

OmniPaxos struct

1

Create a unified `OmniPaxos` struct that has the BLE and SequencePaxos structs as private fields instead. We previously had separated BLE and SequencePaxos as described in the pseudo code. However,...

Currently `OmniPaxos` reads directly from the user-provided `Storage` for variables such as the `promised_round` and `decided_idx`. This will be inefficient if `Storage` is storing these in persistent storage. Thus, `OmniPaxos`...

Have a compilation flag that allows for a "cheap" prepare phase where followers do not send their suffix but only the metadata. The leader then requests the suffix from the...