Details
Major Description
The length of the session command histories of sessions is not visible even though statistics on them are calculated. Exposing the actual values would also allow sessions that use large amounts of them to be spotted more easily.
The 22.08 release includes the size of the history but not how many commands are in it. This makes it hard to tune the worst-case memory usage of MaxScale.
Since the length of the session command history is not directly related to the memory use of the session, the task of tuning max_sescmd_history is not easy. A new parameter that controls it based on the size in bytes (e.g. max_sescmd_history_size) could be added to make it easier.