[MXS-4002] KILL commands leave no trace in the log Created: 2022-02-16  Updated: 2022-02-23  Resolved: 2022-02-23

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.5.19, 6.2.1
Fix Version/s: 2.5.20, 6.2.3

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


 Description   

Executing a KILL command through MaxScale causes some special code to be executed that handles the translation from the session ID used in MaxScale to the real connection ID on the backend servers. As this involves a set of relatively complicated steps, logging some messages on the info log level would help verify that it behaves as expected. Currently there are no messages logged at all for anything related to KILL queries.



 Comments   
Comment by markus makela [ 2022-02-22 ]

This will be fixed as a part of MXS-4004.

Comment by markus makela [ 2022-02-23 ]

Fixed as a part of MXS-4004.

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