Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
N/A
-
None
Description
At the moment, rocksdb.slow_query_log fails with this error:
2016-12-03 17:58:02 139837224450432 [ERROR] /home/psergey/dev-git/10.2
|
mariarocks/sql/mysqld: unknown option '--log-slow-extra'
|
The test itself checks that log-slow-extra produces a few RocksDB-related counters like so:
# # Query_time: 0.022742 Lock_time: 0.000112 Rows_sent: 1 Rows_examined: 7500
|
Thread_id: 2 Errno: 0 Killed: 0 Bytes_received: 0 Bytes_sent: 66 Read_first: 1 Read_last: 0
|
Read_key: 0 Read_next: 7500 Read_prev: 0 Read_rnd: 0 Read_rnd_next: 0 *RocksDB_key_skipped: 9999 *
|
*RocksDB_del_skipped: 2499 *
|
Sort_merge_passes: 0 Sort_range_count: 0 Sort_rows: 0 Sort_scan_count: 0 Created_tmp_disk_tables: 0 Created_tmp_tables: 0 Tmp_table_bytes_written: 0 Start: 22:34:03 End: 22:34:03 Reads: 0 Read_time: 0.000000
|
The patch that introduced this:
https://github.com/facebook/mysql-5.6/commit/8098b78783624f87db83ed9c1022db3ba980f34e
As one can see, the counters are collected/printed in engine-agnostic fashion (despite having names like RocksDB_del_skipped and not having any universal meaning).
The question is, what do we do with this in MariaDB? Introduce a SE API "service" for printing extra stuff into the slow query log?
Attachments
Issue Links
- is part of
-
MDEV-9658 Make MyRocks in MariaDB stable
-
- Closed
-