Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.11, 13.0
-
None
-
Unexpected results
Description
I noticed --master-data and --delete-master-logs both queries SHOW MASTER STATUS.
I was goïng to propose reüsing their short results to avoid an expensive second query, since --delete-master-logs includes --master-data.
But then I reckoned that if the binary log rotates between the two queries, the two results would differ since the first result is stale.
The attached test demonstrates this procedure using Debug Sync.
The results show that --delete-master-logs only deleted the binary log up to File 2 exclusive, even though --master-data outputs CHANGE MASTER TO MASTER_LOG_FILE='File 4'.
Fortunately, this sequencing means the main use of --delete-master-logs is unaffected.
It'd be problematic if the inconsistency is the other way around: --master-data pointing to a file that --delete-master-logs has deleted.
Attachments
Issue Links
- relates to
-
MDEV-7611 [PATCH] mysqldump --dump-slave always starts stopped slave
-
- Closed
-
-
MDEV-32969 Mariadb-dump --delete-master-logs May Not Delete Binary Logs
-
- Open
-
- split from
-
MDEV-39519 Change mariadb-dump to use SHOW REPLICA STATUS instead of SHOW SLAVE STATUS
-
- Closed
-