Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1.36, 10.2.17
-
Linux XXXXX 2.6.32-754.3.5.el6.x86_64 #1 SMP Tue Aug 14 20:46:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
mysql Ver 15.1 Distrib 10.2.17-MariaDB, for Linux (x86_64) using readline 5.1
$ rpm -qa | grep -i mariadb
MariaDB-shared-10.2.17-1.el6.x86_64
MariaDB-server-10.2.17-1.el6.x86_64
MariaDB-client-10.2.17-1.el6.x86_64
MariaDB-test-10.2.17-1.el6.x86_64
MariaDB-compat-10.2.17-1.el6.x86_64
MariaDB-common-10.2.17-1.el6.x86_64
MariaDB-devel-10.2.17-1.el6.x86_64
Linux XXXXX 2.6.32-754.3.5.el6.x86_64 #1 SMP Tue Aug 14 20:46:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mysql Ver 15.1 Distrib 10.2.17-MariaDB, for Linux (x86_64) using readline 5.1 $ rpm -qa | grep -i mariadb MariaDB-shared-10.2.17-1.el6.x86_64 MariaDB-server-10.2.17-1.el6.x86_64 MariaDB-client-10.2.17-1.el6.x86_64 MariaDB-test-10.2.17-1.el6.x86_64 MariaDB-compat-10.2.17-1.el6.x86_64 MariaDB-common-10.2.17-1.el6.x86_64 MariaDB-devel-10.2.17-1.el6.x86_64
Description
Experts,
After applying latest MariaDB patches on Replication master and Replication Slave, we are facing a strange issue.
Once per nearly 3 hours (random time) replication process at slave stopped with following errors
2018-09-04 6:33:28 140064771901184 [ERROR] Error reading packet from server: binlog truncated in the middle of event; consider out of disk space on master; the first event 'XXXXX-bin.000727' at 431628288, the last event read from 'XXXXX-bin.000728' at 399111340, the last byte read from 'XXXXX-bin.000728' at 399111359. (server_errno=1236)
2018-09-04 6:33:28 140064771901184 [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 'XXXXX-bin.000727' at 431628288, the last event read from 'XXXXX-bin.000728' at 399111340, the last byte read from 'XXXXX-bin.000728' at 399111359.', Internal MariaDB error code: 1236
This issue resolves when i submit command "stop slave; start slave;" .
This is something weird and strange because let's assume if problem persists on master replication server how it gone away by "stop slave; start slave;" simple command.
That make me uncomfortable and unconvinced.
thanks
Devang
Attachments
Issue Links
- blocks
-
MDEV-16886 mysqdump --master-data=N crashes when SELECT BINLOG_GTID_POS() returns NULL for current master coordinates, for whatever reason
- Open