[MDEV-29137] mariabackup excessive logging of ddl tracking Created: 2022-07-19  Updated: 2022-07-26  Resolved: 2022-07-25

Status: Closed
Project: MariaDB Server
Component/s: Backup
Affects Version/s: 10.6.6, 10.7.2, 10.8.1, 10.6.7, 10.6.8, 10.7.3, 10.7.4, 10.8.2, 10.8.3, 10.9.1
Fix Version/s: 10.6.9, 10.7.5, 10.8.4, 10.9.2, 10.10.1

Type: Bug Priority: Minor
Reporter: MG Assignee: Thirunarayanan Balathandayuthapani
Resolution: Fixed Votes: 0
Labels: regression-10.6

Issue Links:
Problem/Incident
is caused by MDEV-26326 MDEV-24626 (remove synchronous page0 ... Closed

 Description   

mariabackup writes space id of each table to stdout once per second, despite space id not having changed:

MariaDB [(none)]> select space, name from information_schema.INNODB_SYS_TABLESPACES where space=56;
+-------+--------------------------+
| space | name                     |
+-------+--------------------------+
|    56 | mysql/innodb_index_stats |
+-------+--------------------------+
1 row in set (0.001 sec)

# grep DDL /mnt/holland/mariabackup/20220718_205103/mariabackup.log | 
awk '{print $NF}' | sort | uniq -c | head -3
 
    503 "./mysql/gtid_slave_pos.ibd"
    503 "./mysql/innodb_index_stats.ibd"
    503 "./mysql/innodb_table_stats.ibd"
 
# awk '/DDL.*innodb_index_stats/ {print $7" "$8" "$9}' /mnt/holland/mariabackup/20220718_205103/mariabackup.log | 
sort | uniq -c
 
    503 modify 56 "./mysql/innodb_index_stats.ibd"
 
 
# awk '/DDL.*innodb_index_stats/ {print}' /mnt/holland/mariabackup/20220718_205103/mariabackup.log |
tail -3
 
[00] 2022-07-18 20:54:39 DDL tracking : modify 56 "./mysql/innodb_index_stats.ibd"
[00] 2022-07-18 20:54:40 DDL tracking : modify 56 "./mysql/innodb_index_stats.ibd"
[00] 2022-07-18 20:54:41 DDL tracking : modify 56 "./mysql/innodb_index_stats.ibd"



 Comments   
Comment by Marko Mäkelä [ 2022-07-25 ]

The messages about FILE_MODIFY records were added as part of fixing MDEV-26326.

Those records are not really related to DDL operations, but listing the names of files that were modified since the previous checkpoint, to allow recovery and backup to efficiently reconstruct a mapping from numeric tablespace identifiers to file names.

thiru, can we remove the logging, or do you foresee any need for it?

Generated at Thu Feb 08 10:06:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.