Tag Info

New answers tagged

0

You have to tell the slave what was the last GTID executed on the master when backup was taken. NewSlave > SET GLOBAL gtid_purged="XXXX"; NewSlave > CHANGE MASTER TO MASTER_HOST="10.x.x.x", MASTER_USER="replication", MASTER_PASSWORD="verysecret", MASTER_AUTO_POSITION = 1; NewSlave > START SLAVE; NewSlave ...


0

Though it's an old question, but if you still looking for answer - try percona xtrabackup. If you have MyISAM tables, use --rsync option. With it we achieved almost seamless dump (lock took around 5-10 seconds for DB around 1Gb).


0

On master you need to have those lines: server-id = 1 binlog_do_db = database replicate-do-table = name On slave: server-id = 2 binlog_do_db = database


1

We are using a Galera cluster with 5 nodes that have a load balancer in front of them, that is continously checking all the nodes. Our configuration is that we only have one of the nodes serving a write and read target for the connections from the load balancer and the other nodes are hot standby. But of course Galera also supports multi master read and ...


1

The answer to the first question, as with most issues in computing is: yes, if you have enough resources and time. If the cluster is in some sort of datacenter environment one would hopefully have some sort of out-of-band management interface like dedicated management NICs and/or a KVM system. Modern datacenter management solutions like Intel's ...


0

based on https://mariadb.com/kb/en/mariadb/mariadb-galera-cluster-known-limitations/ "Transaction size. While Galera does not explicitly limit the transaction size, a writeset is processed as a single memory-resident buffer and as a result, extremely large transactions (e.g. LOAD DATA) may adversely affect node performance. To avoid that, the ...



Top 50 recent answers are included