Fake fatal error 1236 from master brakes replication on slave
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Hello.
I've got following error twice on my ~17 slaves host at same time.
I'm sure that I had at least 300Gb free space for mysql logs on master and at least 100Gb space for relay logs on slaves. File system - ext4.
CentOS 6.6 amd64 and Percona server 5.6.23-rel72.1 on both master and slave. After first failure I set "sync_binlog = 1" on master, but this did not helps, second time it fails this friday. Zabbix check free space on master every 300 seconds, I don't think that hundreds of gigabytes could be really exhausted and freed between two check (there are RAID10 with BBU of four disc for logs). I don't have inode monitoring for this filesystem.
The only probably reason for 'out of space' is tmpfs of 2Gb, which is used as tmpdir. Does Percona use tmpfs for replication somehow?
Here if similar complain from MariaDB: https:/
Here is exact error messages:
2015-03-13 17:54:32 14091 [ERROR] Error reading packet from server: binlog truncated in the middle of event; consider out of disk space on master; the first event 'mysql-bin.214657' at 93047076, the last event read from '/var/log/
2015-03-13 17:54:32 14091 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'binlog truncated in the middle of event; consider out of disk space on master; the first event 'mysql-bin.214657' at 93047076, the last event read from '/var/log/
2015-03-27 21:08:57 3014 [ERROR] Error reading packet from server: binlog truncated in the middle of event; consider out of disk space on master; the first event 'mysql-bin.001071' at 81546762, the last event read from '/var/log/
2015-03-27 21:08:57 3014 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'binlog truncated in the middle of event; consider out of disk space on master; the first event 'mysql-bin.001071' at 81546762, the last event read from '/var/log/
Here is part of master config:
server-id = 123
replicate-do-db = advdb
log_bin = /var/log/
max_binlog_size = 100M
expire_logs_days = 1
binlog_do_db = advdb
binlog_format = MIXED
log_slave_updates = On
sync_binlog = 1
Config from master server