June 19, 2013

Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1

… to make the master read-only? Can we use regular replication for some slaves and GTID replication for other slaves at the same… Let’s stop slave #2, change configuration and restart it: mysql> show slave status\G [...] Slave_IO_Running: No Slave_SQL_Running: Yes [...] The error log tells us why…

Post: Choosing a MySQL HA Solution - Post-Webinar Q&A

slave, as described in the MySQL manual. You can configure the slave… you add binary log filters; this … I’d suggest reading over the manual…ERROR] /usr/libexec/mysqld: Incorrect information in file: ‘./mysql/servers.frm’ ERROR: 1033 Incorrect information in file: ‘./mysql/servers.frm’ Running mysql

Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)

…_Log_File: Read_Master_Log_Pos: 4 Relay_Log_File: mysql_sandbox35302-relay-bin.000001 Relay_Log_Pos: 4 Relay_Master_Log_File: Slave_IO_Running: No Slave…04 sec) mysql> show slave status\G Empty set (0.00 sec) mysql> start slave; ERROR 1200 (HY000): The server is not configured as slave; fix in config…

Post: Percona Server for MySQL 5.5.30-30.2 now available

log records are overwritten by the new log data. In some corner cases this could lead to assertion errors in the logslave_max_allowed_packet variable. Bug fixed #1135097 (George Ormond Lorch III). Fixed the upstream bug #62578 which caused MySQL… Bychko). UDF/configure.ac was… internal read operations…

Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue

log records are overwritten by the new log data. In some corner cases this could lead to assertion errors in the logslave_max_allowed_packet variable. Bug fixed #1135097 (George Ormond Lorch III). Fixed the upstream bug #62578 which caused MySQL… Bychko). UDF/configure.ac was… internal read operations…

Post: Percona XtraBackup 2.0.7 for MySQL available for download

log copying thread is now configurable by innobackupex –log-copy-interval. Making the interval configurablelog files were bigger than 4G on the source server. Bug fixed #1164979. Due to different implementation in MySQL 5.6 error

Post: Percona XtraBackup 2.1.0 'release candidate' for MySQL available for download

log copying thread is now configurable by innobackupex –log-copy-interval. Making the interval configurableMySQL 5.6 error messages were not printed to stderr directly. Because of that all InnoDB error

Post: Confusing MySQL Replication Error Message

MySQL Error Messages which are confusing, here is one more: 080603 20:53:10 [Note] SlaveSlave I/O thread: Failed reading log event, reconnecting to retry, log ‘master-bin.003676′ position 444292333 080603 20:53:10 [Note] Slave… is (because of configuration error) two slave servers got the same server…

Post: How to create/restore a slave using GTID replication in MySQL 5.6

… and set it on the slave. MySQL keeps two global variables with GTID… The last step is to configure the slave using the auto-configuration method of GTID: slave1 …Slave_IO_Running: No Slave_SQL_Running: Yes Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: ‘The slave

Post: Find where your data is replicated, win a Percona Live ticket

… ever wondered what servers are in your MySQL replication hierarchy? We have, too. As …slave, has 2 slaves connected, is read_only Filters Binary logging MIXED Slave status 0 seconds behind, running, no errors Slave… your replication hierarchy, how it’s configured, and a few basic bits of status…