[MDEV-13404] MyRocks upstream has I_S.table_statistics.ROW_LOCK*, should we import? Created: 2017-07-30  Updated: 2018-11-27

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - RocksDB
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Sergei Petrunia Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

The upstream has introduced information_schema.table_statistics.row_lock_deadlocks column (as far as I understand it works for any storage engine, they also have it for InnoDB).

They are also using it in mysql-test/include/deadlock_stats.inc, which is used in rocksdb.deadlocks_stats.

For now, I will just comment out the part of the testcase. In the future we should decide whether to

  • Keep not having this feature
  • Port it completely
  • Replace it with something else (why can't RocksDB export a plugin-specific table with deadlock stats).


 Comments   
Comment by Sergei Petrunia [ 2017-07-30 ]

There is also rocksdb.lock_wait_timeout_stats which uses information_schema.table_statistics.ROW_LOCK_WAIT_TIMEOUTS

Generated at Thu Feb 08 08:05:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.