[MXS-3772] Qlafilter message timing is inconsistent Created: 2021-09-16 Updated: 2021-10-11 Resolved: 2021-10-11 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | qlafilter |
| Affects Version/s: | 6 |
| Fix Version/s: | 6.2.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | Niclas Antti |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-141 |
| Description |
|
Depending on the configuration, the messages are either logged before they start or after the first response is received. Logging the message only when it fully completes in all cases would make the latency measurement more accurate and provide similar semantics for the data in all cases. This also solves the problem where queries that fail due to network errors are logged but not really executed. |