>Well, if you’re being smart - do please tell us how Raft solves the problem of online faulty node replacement: I never said that it did. That is what I mean b

>Well, if you’re being smart - do please tell us how Raft solves the problem of online faulty node replacement: I never said that it did. That is what I mean by my statement that more work is required to build a real system in the real world. Much of the code of rqlite is about cluster management, built on a Raft substrate. >how how does it re-sync the current, up-to-date state to the new node I suggest you read the Raft paper, and study the Hashicorp Go implementation (https://github.com/hashicorp/raft https://github.com/hashicorp/raft) to see how this is done. It's all there. >As far as Google went with their paper; they were incredibly correct by saying that actually implementing a distributed system is hard because of the failure modes; rather than the success modes of the running system. I couldn't agree more.