<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Innodb-Cluster on Ivan Luminaria</title><link>https://ivanluminaria.com/en/tags/innodb-cluster/</link><description>Recent content in Innodb-Cluster on Ivan Luminaria</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Oct 2025 08:03:00 +0100</lastBuildDate><atom:link href="https://ivanluminaria.com/en/tags/innodb-cluster/index.xml" rel="self" type="application/rss+xml"/><item><title>Full disk on a MySQL cluster: binary logs, Group Replication, and a migration that leaves no room for mistakes</title><link>https://ivanluminaria.com/en/posts/mysql/mysql-group-replication-binlog-migration/</link><pubDate>Tue, 14 Oct 2025 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/mysql/mysql-group-replication-binlog-migration/</guid><description>&lt;p&gt;The alert came on a Monday morning, wedged between three meetings and a coffee that was still hot. &amp;ldquo;Filesystem /mysql at 85% on the primary node.&amp;rdquo; On another node it was 66%, on the third 25%. In a cluster, when the numbers don&amp;rsquo;t match across nodes, there&amp;rsquo;s always something going on underneath.&lt;/p&gt;
&lt;p&gt;The first question that comes to mind is &amp;ldquo;how much space do we need?&amp;rdquo; But that&amp;rsquo;s the wrong question. The right one is: &amp;ldquo;why is it filling up?&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>