# Replication hangs after mysqldump / innobackupex from master

**URL:** <https://forums.percona.com/t/replication-hangs-after-mysqldump-innobackupex-from-master/1915>\
**Category:** Other MySQL® Questions\
**Created:** [October 11, 2012, 6:02pm UTC](https://forums.percona.com/t/replication-hangs-after-mysqldump-innobackupex-from-master/1915 "2012-10-11T18:02:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebastian](https://avatars.discourse-cdn.com/v4/letter/s/4da419/32.png) [@Sebastian](https://forums.percona.com/u/Sebastian)\
**Post date:** [October 11, 2012, 6:02pm UTC](https://forums.percona.com/t/replication-hangs-after-mysqldump-innobackupex-from-master/1915/1 "2012-10-11T18:02:28Z")

</div>

Hi,

currently we have some problems with the replication of the percona server (Server version: 5.5.27-28.1-log Percona Server (GPL), Release 28.1).  
The problem is that the slave stands still some seconds after the innobackupex backup was copied and the change master & start slave was executed, but only the Exec\_Master\_Log\_Pos hangs, Relay\_Log\_Space is still increasing and in the file system the relay logs are increasing. The configuration (my.cnf) contains exactly the same configuration as the master, we tried also to change the binlog\_format from RAW to MIXED but nothing changed (of course we did the reset master thing after the changes).

We also tried a mysqldump import to the slave but nothing seems to solve the problem.

While the slave is started the mysqld process consumes 100% of one CPU thread, the IO-load itself is low and the server runs with a high performance SSD RAID 5.

Our configuration is as the following:  
key\_buffer = 4096M  
max\_allowed\_packet = 128M  
read\_buffer\_size = 8M  
thread\_stack = 512K  
table\_cache = 48K  
myisam\_sort\_buffer = 70M  
join\_buffer\_size = 1024M  
tmp\_table\_size = 2048M  
max\_heap\_table\_size = 50M  
max\_connections = 300  
innodb\_adaptive\_flushing\_method = keep\_average  
myisam-recover = BACKUP  
query\_cache\_limit = 64M  
query\_cache\_size = 100M  
query\_cache\_type = 1  
server-id = 805  
log\_bin = /var/lib/mysql/percona/logs/master\_805  
expire\_logs\_days = 1  
max\_binlog\_size = 100M  
binlog\_format = MIXED  
innodb\_data\_home\_dir = /var/lib/mysql/percona/innodb/  
innodb\_data\_file\_path = ibdata1:4096M:autoextend  
innodb\_autoextend\_increment = 4096M  
innodb\_log\_group\_home\_dir = /var/lib/mysql/percona/logs/  
innodb\_buffer\_pool\_size = 8192M  
innodb\_additional\_mem\_pool\_size = 1024M  
innodb\_log\_file\_size = 1024M  
innodb\_log\_buffer\_size = 20M  
innodb\_flush\_log\_at\_trx\_commit = 0  
innodb\_lock\_wait\_timeout = 9600  
transaction-isolation = READ-COMMITTED  
innodb\_thread\_concurrency = 12  
innodb\_file\_per\_table  
sort\_buffer\_size = 1024M  
net\_write\_timeout = 3600

We’re currently a bit perplexed and don’t know how to fix this issue, so hopefully you expert guys have an idea what we can do to solve that problem.

Any help would be really welcome!

Thanks,

Sebastian

---

<div class="post-metadata">

**Author:** ![revin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/revin/32/824_2.png) [@revin](https://forums.percona.com/u/revin)\
**Post date:** [October 16, 2012, 12:26am UTC](https://forums.percona.com/t/replication-hangs-after-mysqldump-innobackupex-from-master/1915/2 "2012-10-16T00:26:08Z")

</div>

Hi,

Can you add skip-slave-start on your config, restart MySQL and execute change master to then start slave. See if it works?

---

<div class="post-metadata">

**Author:** ![Sebastian](https://avatars.discourse-cdn.com/v4/letter/s/4da419/32.png) [@Sebastian](https://forums.percona.com/u/Sebastian)\
**Post date:** [October 16, 2012, 9:25am UTC](https://forums.percona.com/t/replication-hangs-after-mysqldump-innobackupex-from-master/1915/3 "2012-10-16T09:25:07Z")

</div>

Hi,

no, unfortunately this doesn’t work, the Exec\_Master\_Log\_Pos stands still and the Relay\_Log increases + the Seconds Behind Master increases all the time. I tried also a reset slave all; and change master to the last position as well as a fresh innobackupex copy but the result is still the same.

Additionally i want to add that we have round about 200 different databases at the master host, we don’t restrict the database replication with do-db / ignore-db settings, etc… Could the amount of databases produce this problem?

Best,

Sebastian