SHOW QUERIESNOTE:
SHOW QUERIESrequires Manticore Buddy. If it doesn't work, make sure Buddy is installed.
SHOW QUERIES returns information about all currently running queries. The output is a table with the following structure:
id: Query ID that can be used in KILL to terminate the queryquery: Query statement or a portion of ittime: Time taken on command execution or how long ago the query was performed (in this case, the value will includeago)protocol: Connection protocol, with possible values beingsphinx,mysql,http,ssl,compressed,replication, or a combination (e.g.,http,sslorcompressed,mysql)host: Client'sip:port
- SQL
- JSON
mysql> SHOW QUERIES;POST /sql?mode=raw -d "SHOW QUERIES"+------+--------------+---------+----------+-----------------+
| id | query | time | protocol | host |
+------+--------------+---------+----------+-----------------+
| 111 | select | 5ms ago | http | 127.0.0.1:58986 |
| 96 | SHOW QUERIES | 255us | mysql | 127.0.0.1:33616 |
+------+--------------+---------+----------+-----------------+
2 rows in set (0.61 sec)[
{
"total": 2,
"error": "",
"warning": "",
"columns": [
{
"id": {
"type": "long long"
}
},
{
"query": {
"type": "string"
}
},
{
"time": {
"type": "string"
}
},
{
"protocol": {
"type": "string"
}
},
{
"host": {
"type": "string"
}
}
],
"data": [
{
"id": 111,
"query": "select",
"time": "5ms ago",
"protocol": "http",
"host": "127.0.0.1:58986"
},
{
"id": 96,
"query": "SHOW QUERIES",
"time": "255us",
"protocol": "mysql",
"host": "127.0.0.1:33616"
}
]
}
]Refer to SHOW THREADS if you'd like to gain insight from the perspective of the threads themselves.
SHOW VERSIONNOTE:
SHOW VERSIONrequires Manticore Buddy. If it doesn't work, make sure Buddy is installed.
SHOW VERSION provides detailed version information of various components of the Manticore Search instance. This command is particularly useful for administrators and developers who need to verify the version of Manticore Search they are running, along with the versions of its associated components.
The output table includes two columns:
Component: This column names the specific component of Manticore Search.Version: This column displays the version information for the respective component.
- SQL
- JSON
mysql> SHOW VERSION;POST /sql?mode=raw -d "SHOW VERSION"+------------+-------------------------------------+
| Component | Version |
+------------+-------------------------------------+
| Daemon | 13.13.4 0bc5a9641@25101507 dev |
| Columnar | columnar 8.1.0 e1522a2@25100213 |
| Secondary | secondary 8.1.0 e1522a2@25100213 |
| Knn | knn 8.1.0 e1522a2@25100213 |
| Embeddings | embeddings 1.0.1 |
| Buddy | buddy v3.35.1+25090418-41d9811f-dev |
+------------+-------------------------------------+[
{
"total": 6,
"error": "",
"warning": "",
"columns": [
{
"Component": {
"type": "string"
}
},
{
"Version": {
"type": "string"
}
}
],
"data": [
{
"Component": "Daemon",
"Version": "13.13.4 0bc5a9641@25101507 dev"
},
{
"Component": "Columnar",
"Version": "columnar 8.1.0 e1522a2@25100213"
},
{
"Component": "Secondary",
"Version": "secondary 8.1.0 e1522a2@25100213"
},
{
"Component": "Knn",
"Version": "knn 8.1.0 e1522a2@25100213"
},
{
"Component": "Embeddings",
"Version": "embeddings 1.0.1"
},
{
"Component": "Buddy",
"Version": "buddy v3.35.1+25090418-41d9811f-dev"
}
]
}
]KILL <query id>KILL terminates the execution of a query by its ID, which you can find in SHOW QUERIES.
- SQL
- JSON
mysql> KILL 4;
Query OK, 1 row affected (0.00 sec)POST /sql?mode=raw -d "KILL 4"
[
{
"total": 1,
"error": "",
"warning": ""
}
]PURGE removes selected data associated with a table. The purge target specifies what is removed.
PURGE <target> FROM TABLE <table_name>;The only target currently supported is BULK_IMPORT.
PURGE BULK_IMPORT FROM TABLE products [OPTION clear_sessions=0|1];PURGE BULK_IMPORT removes the entire staging root used by bulk import, including directories and files left by an interrupted load. Run it only after confirming that no direct-to-disk load is active for the table.
If the table has an open or failed Shared HTTP bulk import pool, the statement is refused. With OPTION clear_sessions=1 it cancels that pool first: unpublished data is discarded, requests still writing to the pool get an error, its indexers are stopped, the table is released for ordinary writes, and then the staging root is removed. Chunks published earlier stay in the table. While the pool is attaching its chunks after a commit, the statement is refused; repeat it after the commit finishes. On Windows, while a request is still writing to the pool, the statement can fail to remove the staging root right after it cancels the pool, because the stopped indexers keep their files open for a moment; repeat it.
An open pool keeps the table reserved, so ordinary writes to it and other bulk imports of it fail, even when all its clients are gone; SHOW LOCKS shows such a table with the lock type write_allow_readers. If the clients stopped or crashed before their commit, this releases the table and discards what they staged:
PURGE BULK_IMPORT FROM TABLE products OPTION clear_sessions=1;To publish the staged documents instead, commit the pool with a request without documents, as described in Shared HTTP bulk import.
OPTION clear_sessions=1 does not cancel private bulk import sessions: a private session releases the table with SET bulk_import=0 or when its connection closes.
The statement requires an existing local real-time table that is not in a replication cluster. It removes only direct-to-disk staging state and does not change the table schema or indexed documents. If the staging root is absent, the statement succeeds without making any changes. In configless mode, DROP TABLE also removes the table's direct-to-disk staging root and cancels its Shared pool.