copycat
copycat copied to clipboard
atomix
A novel implementation of the Raft consensus algorithm
The current implementation of linearizable semantics for clients via sessions follows the Raft dissertation precisely. All commands are logged with a `sequence` number. When a command is applied to the...
`ClusterState` seems to track members of the cluster by their "ID" and the ID seems to be (`LeaderState#join(...)`) the Object#hashCode() of the address of that node. This seems to be...
Generally speaking, the Raft algorithm reads log entries sequentially. When replicating to a follower, the leader reads some number of sequential entries, sends a request, gets a response, and continues....
There is some potential for leaders to be disrupted during configuration changes. Since the leader updates its configuration when it logs the configuration change, servers that are removed from the...
Currently, clients submit keep alive requests at an interval that is a fixed fraction of the session timeout. This places an unnecessary burden on the cluster, particularly if many clients...