[MXS-3147] Pinloki should not create logically empty binlog files. Created: 2020-08-31 Updated: 2020-09-14 Resolved: 2020-09-11 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | pinloki |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | Niclas Antti |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-114 | ||||||||
| Description |
|
Pinloki, or Binlog Router in 2.5 creates a new log every time it reconnects with the master. While this is not a bug, it can be wasteful and potentially cause problems if there are large amounts of reconnects, e.g. during some disturbance in the network. |
| Comments |
| Comment by Niclas Antti [ 2020-09-04 ] |
|
Extending the scope to not only avoid creating "logically" empty binlogs, but appending to the last log file until the master rotates, or a new master takes over. |