[MDEV-18614] Optimization for binlog rotation Created: 2019-02-18 Updated: 2023-11-17 Resolved: 2023-11-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Replication |
| Fix Version/s: | 10.4.4 |
| Type: | Task | Priority: | Major |
| Reporter: | musazhang | Assignee: | Michael Widenius |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | replication | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
When binlog file size exceed max_binlog_size designed by configuration, it will call find_uniq_filename to generate the next binlog file name for next binlog file. In this case, user thread will scan all the files in the binlog directory, which can be found by log_bin_basename. It will cost a lot of time when there are a lot of binlog files exist. and as a result, all DML/DDL will be blocked by this user thread for some time. |
| Comments |
| Comment by Michael Widenius [ 2023-11-17 ] |
|
The speedup of binlog rotations was already done in 10.4.4 as part of |