Sumukha Pk
Sumukha Pk
Will implement the raft protocol once complete based on the design doc in `doc/internal/consensus` - [ ] Code correctness - [ ] Documentation - [ ] Test cases
The first step towards having a consensus protocol running. This'll serve as a spec to be followed for implementation. Updates to this doc will be done when needed to accommodate...
Specifically here: https://github.com/tomarrell/lbadd/blob/raft/internal/node/node.go#L98 The old `Execute` function is obsolete. Once `engine` is merged to master, we need to add the replication link appropriately.
To setup a thorough raft integration test we need the following up: - [ ] A generic integration testing framework that uses actual multiple servers. (#175 ) - [ ]...
This module must be able to kill any random server, probably multiple at a time and observe the operations that proceed.
This framework must be able to spawn multiple servers using the `internal/node` API and start the raft server operations on the cluster.
We need extensive integration tests on the raft cluster covering all possibilities. The test must use the underlying `cluster` package and actually create clusters instead of mocking them. Following are...
This will be a progress tracker for implementation of raft. This doesn't include tests, it's a separate issue (#125 ) though this is a part of #121. - [ ]...
I was wondering how long inputs are handled here. I've seen some CL commands fill the current screen and then on press of a `return` print the extra line while...
Is there a way to obtain the arguments on the function call of the mocked variable? This soooo helps out during testing.