June 18, 2013

Post: How does MySQL Replication really work?

log written by a master) Read_Master_Log_Pos – binary log from master is copied over to the relay logExec_Master_Log_Pos – which position from master binary log is being executed by SQL thread. Replication lag Now I want to briefly touch the subject of replication

Post: Can MySQL temporary tables be made safe for statement-based replication?

Master_Log_File: mysql-bin.000006 Read_Master_Log_Pos: 98 Relay_Log_File: mysql_sandbox20551-relay-bin.000028 Relay_Log_Pos: 235 Relay_Master_Log_File: mysql

Post: Debugging problems with row based replication

log.  Since row-based logs only contain information about changed rows, a replicationmaster log mysql-bin.000001, end_log_pos 340718 This error message is telling us that a row that was modified on the masterlog_pos 340637        Query   thread_id=6     exec

Post: Ultimate MySQL variable and status reference list

MySQLread_ahead_thresholdblogpercona.commanual innodb_read_io_threadsblogpercona.commanual innodb_replicationmaster_infoblogpercona.commanual sync_relay_logblogpercona.commanual sync_relay_log

Post: How SHOW SLAVE STATUS relates to CHANGE MASTER TO

Master logs (Master_Log_File:Read_Master_Log_Pos) and SQL Thread position in Master logs (Relay_Master_Log_File:Exec_Master_Log_Pos). When you’re using CHANGE MASTER

Post: Replication checksums in MySQL 5.6

… Relay_Master_Log_File and Exec_Master_Log_Pos from SHOW SLAVE STATUS slave1 [localhost] {msandbox} ((none)) > change master to master_log_file=’mysql-bin.000001′, master_log_pos=2690… Could not read entry at offset 283: Error in log format or read error. [...] Replication checksums on the master We …

Post: Using Flexviews - part two, change data capture

replicationmysql -e ‘select * from flexviews.binlog_consumer_status\G’ -uroot *************************** 1. row *************************** server_id: 999 master_log_file: binary_log.000001 master_log_size: 214652 exec_master_log_pos

Post: How to know if you're updating Slave you should not ?

… to the slave. Of course there is read_only setting which is good to set … By default MySQL will only write statements which come to the server directly (not via replication thread) …Master and another on Slave directly: # at 666 #100411 19:24:01 server id 1 end_log_pos 725 Query thread_id=68 exec