As explained in this previous post, it’s now (since 8.0.16) possible to use the MySQL Shell Reporting Framework to monitor MySQL InnoDB Cluster. Additionally, when a member of the MySQL InnoDB Cluster’s Group leaves the group for any reason, or when a new node is added from a backup, this member needs to sync up with the other nodes of … Read More
With MySQL Shell 8.0.16, a new very interesting feature was released: the Reporting Framework. Jesper already blogged about it and I recommend you to read his articles if you are interested in writing your own report: https://mysql.wisborg.dk/2019/04/26/mysql-shell-8-0-16-built-in-reports/ https://mysql.wisborg.dk/2019/04/27/mysql-shell-8-0-16-user-defined-reports/ I this post, I will show you one user-defined report that can be used to monitor your MySQL InnoDB Cluster / Group … Read More
We saw yesterday that when an issue (like network splitting), it’s possible to remain with a partitioned cluster where none of the partition have quorum (majority of members). For more info read how to manage a split-brain situation.
Everywhere I go to present MySQL InnoDB Cluster, during the demo of creating a cluster, many people doesn’t understand why when I’ve 2 members, my cluster is not yet tolerant to any failure.
Consistency during reads have been a small concern from the adopters of MySQL InnoDB Cluster (see this post and this one). This is why MySQL supports now (since 8.0.14) a new consistency model to avoid such situation when needed. Nuno Carvalho and Aníbal Pinto already posted a blog series I highly encourage you to read: Group Replication – Consistency Levels … Read More