Mysql Master - Master Replication and mysql-bin.log Rotation issues

Mysql Master - Master Replication and mysql-bin.log Rotation issues - mysql

I have successfully synced my primary and secondary databases using Mysql Master - Master Replication( guide: https://www.digitalocean.com/community/tutorials/how-to-set-up-mysql-master-master-replication ). Well I am stuck with a weird issue. Every time the mysql service is restarted the value of mysql-bin.xxxxxx file gets incremented(eg: mysql-bin.000005 to mysql-bin.000006) and it stops the master - master replication process. How can I prevent the mysql-bin file value rotation or is there any way to deal with this increment issue so that even if the rotation happens the replication wont get affected?
Thanks :)
Update
As usual I had to find the answer for my own question, here is the solution for those who are facing the same situation. Just added the line log_slave_updates=1 to my.cnf file in both the servers.
Master - Master Repication:
Primary my.cnf:
#bind-address=127.0.0.1
server-id=1
log_bin=/var/log/mysql/mysql-bin.log
binlog_do_db=db_name_1
binlog_do_db=db_name_2
binlog_do_db=db_name_3
max_binlog_size=100M
log_slave_updates=1
auto_increment_increment=2
auto_increment_offset=1
Secondary my.cnf:
#bind-address=127.0.0.1
server-id=2
log_bin=/var/log/mysql/mysql-bin.log
binlog_do_db=db_name_1
binlog_do_db=db_name_2
binlog_do_db=db_name_3
max_binlog_size=100M
log_slave_updates=1
auto-increment-increment=2
auto-increment-offset=2

Related

MySQL Master-Slave Replication When Master is Down

I'm running MySQL as the database on Ubuntu instances. I'm using MySQL Master-Slave replication where master's changes will be written to slave and slave's changes will not be reflected on the master. That's fine. I'm using a HAProxy load balancer to front the MySQL instances where all the requests will be sent to master MySQL instance. If the master MySQL instance is down slave MySQL instance will act as master and HAProxy will send all the requests to salve. Active-Passive scenario.
HAProxy - 192.168.A.ABC
MySQL Master - 192.168.A.ABD
MySQL Slave - 192.168.A.ABE
Let's assume that the MySQL master(192.168.A.ABD) is down. Now all the requests will be sent to MySQL slave(192.168.A.ABE) by HAProxy where now he acts as the master MySQL server for the time being.
My problems are
What happens when original master MySQL instance(192.168.A.ABD) is up?
Will changes written to new MySQL master (192.168.A.ABE) be replicated to original master(192.168.A.ABD) again?
How should I address this scenario?

First of all I should say that I have never used HA Proxy so con't comment on that directly.
However, in your current setup the Master (ABD) will be out of sync, and wont catch up. You will have to rebuild that using mysqlDump or similar tool.
What you would need is a Master < > Master setup (as opposed to Master > Slave), which enables you to write to either database and have it reflected in the other. This isn't quite as straight forward as it sounds though.
Assuming you already have your master > slave setup, and they are in sync
On the Master (ABD) you want to add:
auto_increment_increment=2
auto_increment_offset=1
log-slave-updates
On the Slave (ABE) add:
auto_increment_increment=2
auto_increment_offset=2
log-slave-updates
to your my.cnf files. Restart the Database. This will help to prevent Duplicate Key Errors. (n.b. that log-slave-updates isn't strictly required but makes it easier to add another slave in future)
Next you want to tell the Master (ABD) to replicate from the Slave (ABE).
Depending on what version of MySQL and if you are using GTID etc. the exact process differs slightly. But basically you are going to issue a CHANGE MASTER statement on the Master so it replicates from the slave.
And away you go. You probably want to avoid writing to both at the same time as that opens up a whole other kettle of fish. But if the Master goes down, you can switch your writes to the slave, and when the master comes back up, it will simply start replicating the missing data.

I am considering you scenario
Master - 192.168.A.ABD
Slave - 192.168.A.ABE
You cannot directly add the master in system. To Add master in system you need to perform below steps:
1) When master is up you can add this as a slave. So now this happens
Master - 192.168.A.ABE
Slave - 192.168.A.ABD
2) Then Now U can put master Down. Means You can put 192.168.A.ABD Down
3) Then Again Add this as slave. So After this You will get below scenarion
Master - 192.168.A.ABD
Slave - 192.168.A.ABE
You can refer this link
https://dev.mysql.com/doc/refman/5.5/en/replication-solutions-switch.html

Master to Master Replication: Clogged until restart

I have got master - to master replication installed.
It all works fine, until you break the link between two servers.
Once it's broken the data won't go from one to another if it exceeds some kind of limit.
Max_packet size is set to 500mb.
However, if you restart the server (mysqld) where the data is clogged (on secondary) it will push it throught.
Nothing in the log file related to this.. Any ideas?
Configuration for primary:
[mysqld]
innodb_file_per_table=1
server-id=6935500
log_bin=mysql-bin
binlog_format=ROW
log_error=/var/log/mysql-bin.err
#binlog_do_db=devjump_dev
binlog_do_db=crm_live
max_allowed_packet=500M
Configuration for secondary
[mysqld]
bind-address=0.0.0.0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
server-id=574271
log_bin=mysql-bin.log
binlog_format=ROW
binlog_do_db=crm_live
max_allowed_packet=500M
log_error=/var/log/mysql-bin.err
relay-log=mysqld-relay-bin
So apparently, after we break a link between these two some big packets are not being pushed into the binlog... From Primary to Secondary.
Thanks Guys,
Roman

After spending lots of hours reading and searching I have discovered that there was an issue with slave-net-timeout
It was defaulted to 3600 so it took 1 hour for the Secondary to find out there was a lag in the connection.
Resetting this to 60 seconds helped big time.
Hopefully someone might find this post useful and it will save their time.