Timeline for What are the drawbacks of using Galera Cluster instead of Master/Slave Replication?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 21, 2021 at 11:12 | comment | added | Deezzle LuBimkii |
@LukeCousins It seems wsrep_causal_reads has been deprecated and now we should use wsrep-sync-wait to enable Galera transmit worksets synchronously. (Source : galeracluster.com/library/documentation/…). For options on how to use wsrep-sync-wait see galeracluster.com/library/documentation/….
|
|
| Apr 14, 2014 at 14:10 | comment | added | Luke Cousins |
In case anyone else is looking, the option that Bill is referring to is wsrep_causal_reads... set to ON with SET GLOBAL wsrep_causal_reads = 'ON'; to get selects to wait until all write sets are done.
|
|
| Dec 7, 2013 at 18:15 | comment | added | Bill Karwin | @jynus, the issue is not locking on the donor node, but that the receiving node is offline and unavailable for any queries while the SST is in progress. Therefore if you're using the cluster for query load balancing, the queries that would have gone to the receiving node have to be sent to other node(s) until the SST is done. | |
| Dec 7, 2013 at 11:54 | comment | added | jynus | @RolandoMySQLDBA SST methods like xtrabackup precisely avoid locking the donor. Although it is true that in any case, the donor will have degraded performance if the database is large. | |
| Dec 7, 2013 at 2:44 | comment | added | RolandoMySQLDBA | Another drawback is having a donor node off itself and be used to copy (via xtrabackup, rsync,mysqldump) to any node introduced to the cluster, leaving the remaining nodes in the cluster to do the heavy lifting until the new node is in sync. It's not such a drawback for small or medium sized DBs. | |
| Dec 6, 2013 at 22:34 | vote | accept | Sam | ||
| Dec 6, 2013 at 22:34 | history | answered | Bill Karwin | CC BY-SA 3.0 |