4 ms·

But the main point made by the parent is entirely correct: the biggest issue isn’t that of implementing a consensus protocol: the biggest issue is the reconfigu

But the main point made by the parent is entirely correct: the biggest issue isn’t that of implementing a consensus protocol: the biggest issue is the reconfiguration of the cluster, management of the dead/live nodes, addition of extra nodes for replacement, copying of the data before reconfiguration. All of that needs tooling.

peterwwillis 7y ago
Yep! And you need someone to help fix bizarre bugs in core that only crop up in your own weird environment. With support that's quick & easy, but otherwise you have to form your own dev team to specialize in it, making it costlier.
linsomniac 7y ago
Indeed. I was reading the dqlite page thinking "where is the monitoring endpoint to tell if the cluster is healthy or degraded?" Too often that seems like an afterthought if it's thought of at all. I have a teeny, tiny cluster using MySQL+galera as a multi-master cluster, but it took a while to iterate to monitoring that tells me when one node is unhealthy and getting the correct repair and restart procedures.
- otoolep 7y ago
  Totally. FWIW, I built all the functionality into rqlite from the very start, for exactly those reasons. In the real world a database must be operated. https://github.com/rqlite/rqlite/blob/master/DOC/DIAGNOSTICS.md https://github.com/rqlite/rqlite/blob/master/DOC/DIAGNOSTICS... https://github.com/rqlite/rqlite/blob/master/DOC/CLUSTER_MGMT.md https://github.com/rqlite/rqlite/blob/master/DOC/CLUSTER_MGM...
gigatexal 7y ago
Needs a Kubernetes operator for sure.