[MDEV-6947] MariaDB on a fuser.glusterfs volume produces: "Got fatal error 1236 from master when reading data from binary log..." Created: 2014-10-27 Updated: 2014-11-24 Due: 2014-11-24 Resolved: 2014-11-24 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Replication |
| Affects Version/s: | 10.0.10 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Erik Wasser | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Debian 7 with /var/lib/mysql on a fuse.glusterfs mount |
||
| Description |
|
We're doing here a MariaDB 10.0.10 setup (both server/client) with replication. Suddenly - out of the blue - the replication fails with the following error message: 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.000073' at 39362449, the last event read from 'mysql-bin.000073' at 48667806, the last byte read from 'mysql-bin.000073' at 48668672.' After a "slave start" on the slave everything works smoothly again. Everything runs fine for days or weeks and suddenly the same error message appears again (with different numbers of course). The volumes (server and client) are large enough to keep the data at everytime so I think this error message just covers some other (real) error. What can I do to pin down this error? |
| Comments |
| Comment by Elena Stepanova [ 2014-10-27 ] |
|
Hi, Did you check system logs for any IO errors? (It seems obvious but since you haven't mentioned it I have to ask). |
| Comment by Elena Stepanova [ 2014-11-24 ] |
|
Closing as incomplete for now, please comment to re-open if you have more information. |