[MXS-4749] log_throttling should be disabled if log_info is on Created: 2023-09-11 Updated: 2023-09-14 Resolved: 2023-09-14 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.5.28, 6.4.10, 22.08.8, 23.02.4, 23.08.0 |
| Fix Version/s: | 2.5.29, 6.4.11, 22.08.9, 23.02.5, 23.08.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
If log_info is enabled and the log_thottling limit is hit, the context of the info level messages is lost for all warnings. For example, authentication failures start to look like a dropped TCP connection when the throttling limit is hit. Since log_info is designed to be verbose, it should disable log_throttling while it's enabled. |