[MXS-1452] Add support for KILL QUERY <id> Created: 2017-09-26 Updated: 2017-12-01 Resolved: 2017-10-03 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.2.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
When a KILL QUERY <id> is executed, MaxScale must change the ID given in the statement to the corresponding connection ID on the correct backend. This can be done by creating a one-to-many relation of internal session IDs to backend server IDs. All of the information required to implement this, namely the connection ID, is already collected by MaxScale and only the mapping of these IDs needs to be added. The problematic part is how to expose the session ID mapping in a consistent way. |
| Comments |
| Comment by markus makela [ 2017-09-29 ] |
|
Added support for KILL [ HARD | SOFT ] [ QUERY | CONNECTION ] <id>. The user specific variant does not yet function but it only requires small changes in MaxScale. The query ID variant would require tracking of query IDs which aren't guaranteed to be unique across multiple MariaDB instances. This poses a problem as there's no way to do a one-to-one or one-to-many mapping of the ID given by the client to the actual query ID on the backend server. A workaround to this problem would be to use a routing hint to route the query to the correct server. |
| Comment by markus makela [ 2017-10-03 ] |
|
Added KILL USER <name>. |