You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use --oltp-skip-trx=on option to avoidBEGIN statement that will start one transaction because I need to do performance test in read-write spilt scenario. But when I set num-threads up to 12, errors ocur:
ALERT: Error 1062 Duplicate entry '38262' for key 'PRIMARY'
FATAL: failed to execute function `event': (null)
Yes, with --oltp-skip-trx=on duplicate key errors are expected for the oltp.lua script, because nothing prevents multiple connections inserting and committing a row with the same key. Without that option each transaction is idempotent, because it inserts and then deletes a row with the same key.
Looking at the patch, that would work, but it seems like your are looking at some fairly old code snapshot. The current source tree supports the --mysql-ignore-errors option that has been implemented for precisely this purpose.
Can you try --mysql-ignore-errors=1042 on the current git HEAD?
OK, --mysql-ignore-errors=1062 ignore the duplicate entry error successfully! Actualy, I have modified that patch to ignore this error, but --mysql-ignore-errors seems more general.
This is the problem. Before this, I have tried ./bin/sysbench --test=oltp help and ./bin/sysbench --test=dir/oltp.lua to get help. No help text:
PANIC: unprotected error in call to Lua API (cannot open oltp: No such file or directory)
Glad --mysql-ignore-errors works for you. But I agree, while documentation is long overdue, there should be at least a way to discover them with sysbench help. I reported #25. Closing this one.
I use
--oltp-skip-trx=on
option to avoidBEGIN
statement that will start one transaction because I need to do performance test in read-write spilt scenario. But when I setnum-threads
up to 12, errors ocur:My sysbench version: 0.5
Work statement:
And does this patch work: ignoreduplicates.patch ?
THANK YOU!
The text was updated successfully, but these errors were encountered: