<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 12, 2020 at 9:47 AM Diego Zuccato <<a href="mailto:diego.zuccato@unibo.it">diego.zuccato@unibo.it</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Il 10/10/20 16:53, Alex K ha scritto:<br>
<br>
> Reading from the docs i see that this is not recommended?<br>
IIUC the risk of having partially-unsynced data is is too high.<br>
DB replication is not easy to configure because it's hard to do well,<br>
even active/passive.<br>
But I can tell you that a 3-node mariadb (galera) cluster is not hard to<br>
setup. Just follow one of the tutorials. It's nearly as easy as setting<br>
up a replica3 gluster volume :)<br>
And "guarantees" consinstency in the DB data.<br></blockquote><div>I see. Since I will not have only mariadb, then I have to setup the same replication for postgresql and later influxdb, which adds into the complexity. <br></div><div>For cluster management I will be using pacemaker/corosync. <br></div><div><br></div><div>Thanx for your feedback<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-- <br>
Diego Zuccato<br>
DIFA - Dip. di Fisica e Astronomia<br>
Servizi Informatici<br>
Alma Mater Studiorum - Università di Bologna<br>
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy<br>
tel.: +39 051 20 95786<br>
</blockquote></div></div>