<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Parallel on FromDual GmbH</title><link>https://www.fromdual.com/tags/parallel/</link><description>Recent content in Parallel on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Tue, 09 Apr 2024 10:53:32 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/parallel/index.xml" rel="self" type="application/rss+xml"/><item><title>MariaDB's parallel replication to catch up</title><link>https://www.fromdual.com/blog/mariadbs-parallel-replication-to-catch-up/</link><pubDate>Tue, 09 Apr 2024 10:53:32 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/mariadbs-parallel-replication-to-catch-up/</guid><description>&lt;p&gt;Due to an application error, our replication stopped for 5 days (over Easter). After the problem was solved, the replication was supposed to catch up, which turned out to be very slow. All the usual tricks (&lt;code&gt;innodb_flush_log_at_trx_commit&lt;/code&gt;, &lt;code&gt;sync_binlog&lt;/code&gt;, etc.) had already been exhausted. So we tried our hand at parallel replication of the MariaDB server.&lt;/p&gt;</description></item></channel></rss>