[MXS-4840] Session command history length tracking is broken Created: 2023-10-27  Updated: 2024-01-02  Resolved: 2023-12-13

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 23.08.1
Fix Version/s: 24.02.0

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-196, MXS-SPRINT-197

 Description   

The session command history maximum and average length tracking is broken in 23.08 and both are always reported as 0. Since the session command history has been a generic feature since MaxScale 6, the tracking of it (if deemed necessary) should be moved there.


Generated at Thu Feb 08 04:31:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.