sysbench icon indicating copy to clipboard operation
sysbench copied to clipboard

COMMIT failed in OLTP Read Only

Open mronstro opened this issue 3 years ago • 1 comments

I get this error message when running sysbench as part of RonDB. I get the error both in Mac OS X on x86_64 as well as using Ubuntu 22.04.1 on WSL 2 in Windows. In both cases it works to insert data, but fails on this during benchmark execution.

FATAL: mysql_stmt_execute() returned error 1210 (Incorrect arguments to with cursor) for query 'COMMIT' FATAL: `thread_run' function failed: .../Cellar/sysbench/1.0.20_3/share/sysbench/oltp_common.lua:409: SQL error, errno = 1210, state = 'HY000': Incorrect arguments to with cursor

Here are the libraries used by sysbench: (base) Mikaels-iMac:log mikael$ otool -L /usr/local/bin/sysbench /usr/local/bin/sysbench: /usr/local/opt/mysql-client/lib/libmysqlclient.21.dylib (compatibility version 21.0.0, current version 21.0.0) /usr/local/opt/zlib/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.12) /usr/local/opt/zstd/lib/libzstd.1.dylib (compatibility version 1.0.0, current version 1.5.2) /usr/local/opt/[email protected]/lib/libssl.1.1.dylib (compatibility version 1.1.0, current version 1.1.0) /usr/local/opt/[email protected]/lib/libcrypto.1.1.dylib (compatibility version 1.1.0, current version 1.1.0) /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/local/opt/libpq/lib/libpq.5.dylib (compatibility version 5.0.0, current version 5.14.0) /usr/local/opt/luajit/lib/libluajit-5.1.2.dylib (compatibility version 2.1.0, current version 2.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.100.5)

Pretty sure it used to work, so a bit lost to what's going on here.

mronstro avatar Nov 30 '22 23:11 mronstro

Incorrect arguments to with cursor looks like it should have been Incorrect arguments to %s with cursor. Maybe that's something with RonDB? Anything in the server logs?

Looks like this is a prepared statement, with the statement being COMMIT, which is not what I would expect.

A traffic capture would also be useful to see if this is a client (likely) or server (unlikely) issue.

dveeden avatar Jun 12 '23 21:06 dveeden