[MXS-3037] show detail processlist like at mariadb Created: 2020-06-12 Updated: 2021-10-20 Resolved: 2021-10-14 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | maxadmin, maxctrl |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | febriyant | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
CentOS 7 |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Sprint: | MXS-SPRINT-142 | ||||||||||||||||
| Description |
|
on mariadb when i need check what are query is running on mariadb instance. But after mariadb connect to maxscale i can't see process list like that. any advice ? |
| Comments |
| Comment by markus makela [ 2020-06-12 ] | |||||||
|
You can use maxctrl show sessions. We don't have SQL commands like SHOW PROCESSLIST. | |||||||
| Comment by febriyant [ 2020-06-13 ] | |||||||
|
but part of queries is empty. how i see like on show processlist on mariadb ? | |||||||
| Comment by markus makela [ 2020-06-13 ] | |||||||
|
I think if you add retain_last_statements=20 and dump_last_statements=on_error under the [maxsacle] section, it should show up. By default most of the time MaxScale doesn't keep the queries in memory while they're executed. If possible, can you add the configuration you used to test this? | |||||||
| Comment by febriyant [ 2020-06-15 ] | |||||||
|
I already set that parameter. so there is queries is still running or sleep ?? | |||||||
| Comment by markus makela [ 2020-08-20 ] | |||||||
|
That is simply the list of queries that was executed. I'll convert this into a feature request as there is no SHOW PROCESSLIST in MaxScale. | |||||||
| Comment by markus makela [ 2021-08-06 ] | |||||||
|
This should be possible to implement purely in MaxCtrl as the query tracking is already implemented in MaxScale as a part of retain_last_statements. I created an initial patch on the MXS-3037 branch that adds the list queries command. The output of the command is as follows:
| |||||||
| Comment by markus makela [ 2021-10-11 ] | |||||||
|
This should be a small enough of an addition that it can go into 6.2. This is only a client-side change and requires no changes in MaxScale itself. |