Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have 2 CentOS 5.5 servers runnig Mysql 5.5, configured as master-master replication. When on one server i have network problems, on another i see messages in log:

111105 2:38:30 [Note] Stop asynchronous binlog_dump to slave (server_id: 2)

when network problems gone, replication dont resume automatically, but it will start in a hour:

111105  3:37:41 [Note] Start binlog_dump to slave_server(2), pos(mysql-bin.000157, 344487149)
111105  3:37:41 [Note] Start asynchronous binlog_dump to slave (server_id: 2), pos(mysql-bin.000157, 344487149)

I think it is just configured timer, but which? Below is mysql configuration:
serv-01:

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
symbolic-links=0

plugin-load=archive=ha_archive.so;blackhole=ha_blackhole.so

#Replication
old_passwords=1
log-bin=/var/lib/mysql/mysql-bin
expire_logs_days=3
binlog-do-db=roomserv
binlog-do-db=asterisk
binlog-ignore-db=mysql
binlog-ignore-db=information_schema
server-id=1
auto_increment_increment= 2
auto_increment_offset   = 1

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

serv-02:

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
symbolic-links=0

#Replication
old_passwords=1
server-id=2

log-bin=/var/lib/mysql/mysql-bin
expire_logs_days=3
binlog-do-db=roomserv
binlog-do-db=asterisk
binlog-ignore-db=mysql
binlog-ignore-db=information_schema

#auto increment id offset
auto_increment_increment= 2
auto_increment_offset   = 2


[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
share|improve this question

1 Answer 1

There were several changes in MySQL 5.5. replication. One is a master heartbeat.

See: http://blogs.oracle.com/MySQL/entry/mysql_55_whats_new_in_replication

However, I am not that is your issue. Given the early AM time stamps on these events are their backups, cron jobs or other service restarts that may be triggering this?

I wonder if the new semi-sync method may be causing issues in the master-master setup.

More on that here: http://dev.mysql.com/doc/refman/5.5/en/replication-semisync.html

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.