<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Galera on Ivan Luminaria</title><link>https://ivanluminaria.com/en/tags/galera/</link><description>Recent content in Galera on Ivan Luminaria</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 17 Feb 2026 08:03:00 +0100</lastBuildDate><atom:link href="https://ivanluminaria.com/en/tags/galera/index.xml" rel="self" type="application/rss+xml"/><item><title>Galera Cluster with 3 nodes: how I solved a MySQL availability problem</title><link>https://ivanluminaria.com/en/posts/mysql/galera-cluster-3-nodi/</link><pubDate>Tue, 17 Feb 2026 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/mysql/galera-cluster-3-nodi/</guid><description>&lt;p&gt;The ticket was laconic, as it often is when the problem is serious: &amp;ldquo;The database went down again. The application is stopped. Third time in two months.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The client had a MariaDB on a single Linux server — a business management application used by about two hundred internal users, with load spikes during end-of-month accounting closures. Every time the server had a problem — a disk slowing down, a system update requiring a reboot, a process consuming all the RAM — the database crashed and with it the entire business operations.&lt;/p&gt;</description></item></channel></rss>