[MDEV-12340] mysqldump with single-transaction on slave doesn't stop applying binlogs Created: 2017-03-23 Updated: 2017-03-23 Resolved: 2017-03-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Backup, Replication |
| Affects Version/s: | 10.1.22 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Pavel Kaidalov | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | replication | ||
| Environment: |
CentOS 7 x86_64 |
||
| Description |
|
I have MariaDB replica server for making consistent database dumps, and after the latest update I noticed that mysqldump with --single-transaction option does not stop applying binary logs, e.g. Seconds_Behind_Master not increasing and Exec_Master_Log_Pos counter increasing during dump. I have all data in INNODB tables, and such --single-transaction behaviour looks odd. My mysqldump options are: Changing --single-transaction to --lock-all-tables - locking tables, and I see correct blocking database from changes during mysqldump. Please check current mysqldump with --single-transaction option behaviour. |
| Comments |
| Comment by Daniel Black [ 2017-03-23 ] |
|
This is correct. The nature of single-transaction is that other transactions started after the dump are not visible to the dump. This applies whether they are entered by replication or by any other slave activity. To verify this look at the mysqldump file for row changes that occurred via replication after the dump was started. |