While Jepsen (and this article) is focused on behavior under node failure and network partitions, this caught my eye:

> It also exhibits Stale Read, Lost Update, and other forms of G-single in healthy clusters

This looks like quite a fundamental issue.

I would kinda expect that. MySQL hasn't been designed to be a distributed database from the beginning and it's usually hard to make it work later on.

I really like glaera for low volume clustering, because of the true multi-master nature. I've been using it for over a decade on a clustered mail server for storing account information, and more recently I've pumped the log information in there so each user can see their related log messages, for a user base of around 6,000 users, and it's been a real workhorse.

I realize that we like to use the page title here on HN, but this really should be something like "Data loss cases with MariaDB Glaera Cluster 12.1.2".