June 18, 2013

Post: Automation: A case for synchronous replication

to MySQL Replication based solution. With MySQL Replication you have to have one Master node which handles traffic. You may be able to send some traffic to Slaves

Post: Percona XtraDB Cluster: Failure Scenarios with only 2 nodes

to run the master and slave IPS and will accept writes. But what could happen with Galera replicationswitchAnd if you test to use the mysql server: [root@percona1 ~]# mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL

Post: MySQL Backup tools used by Percona Remote DBA for MySQL

replicating out to all slaves mysqlbinlog 5.6 Last year Percona IT director Tamas Kozak had a great blog post that showed howmaster and slave Re-transfer files that are partially transferred Compress the files after successful transfer Amazon S3 for MySQL

Post: Read/Write Splitting with PHP Webinar Questions Followup

MySQL replicationswitch between different modes on successive queries. Q: Is RBR faster replicating vs SBR replicationto the slave‘s system clock and get a much more reliable measure of slave lag (assuming the system clocks on master and slave

Post: MySQL Master-Master replication manager released

master-master and bunch of slaves. Typically you would define “roles” for example READER and WRITER roles for most simply case and assign them toswitch happens “dirty” way potentially risking replication inconsistencies. This is very handy if you want to restart one of servers in clusters to

Post: Faster MySQL failover with SELECT mirroring

MySQL configurations for high availability is master-master replication, which is just like normal master-slave replicationto watch the traffic on the active master and replay SELECT queries against the passive one. I timed the results and

Post: MySQL Northern European Customer Conference

switch from MyISAM to Falcon. It was rather interesting to hear a lot about features of new storage engines such as Nitro andMySQL Enterprise from MySQL Marketing Materials . There is not much of technical insight otherwise – pretty simple site, master slave replication, plans to

Post: Recovery beyond data restore

switch to the slave in this case is not very easy too – all slaves can be on different positions at the master and you need tomaster (and they will be replicated down to all slaves) the faster however (especially if you have many tiers of replication) is to bring all slaves to

Post: Heikki Tuuri answers to Innodb questions, Part II

replication slave. Can you make the reorganization run in a tolerable time? PZ: Indeed using master-master setup and switching roles is a good way to get large data manageable. MySQL Master Master Manager can help you to

Comment: Small things are better

and processors, in a dual-master-slave configuration. One acts as a primary and one as a backup. If one fails, I can switch over toto the other. But then the problem is, how… a third and fourth replication slave, one on-site and one off… shut down MySQL on one of the backup slaves and synchronize the…