Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
13.1
-
None
-
None
Description
If I run TPCC benchmark provided by https://github.com/cmu-db/benchbase project, the error log is spammed with
``
2026-06-10 17:54:49 65 [ERROR] Got error 123 when reading table '.\benchbase\stock'
2026-06-10 17:55:40 71 [ERROR] Got error 123 when reading table '.\benchbase\stock'
2026-06-10 17:55:47 72 [ERROR] Got error 123 when reading table '.\benchbase\stock'
2026-06-10 17:56:05 72 [ERROR] Got error 123 when reading table '.\benchbase\stock'
2026-06-10 17:56:08 73 [ERROR] Got error 123 when reading table '.\benchbase\stock'
2026-06-10 17:56:11 78 [ERROR] Got error 123 when reading table '.\benchbase\stock'
2026-06-10 17:56:31 71 [ERROR] Got error 123 when reading table '.\benchbase\stock'
2026-06-10 17:56:33 72 [ERROR] Got error 123 when reading table '.\benchbase\stock'
``
If I switch innodb_snapshot_isolation OFF, it does not happen.
diego dupin has a writeup on how to run this benchmark here https://mariadb.com/resources/blog/how-to-benchmark-mariadb-mysql-using-java-connector/
Attachments
Issue Links
- relates to
-
MDEV-35124 Set innodb_snapshot_isolation=ON by default
-
- Closed
-
-
MDEV-39991 benchbase TPCC runs onto unexpected response when innodb_snapshot_isolaton is ON
-
- Open
-