I'm benchmarking MySQL under different isolation levels.
For the case of SERIALIZABLE I frequently get this error: "Deadlock found when trying to get lock; try restarting transaction at the client side".
Reading http://dev.mysql.com/doc/refman/5.6/en/innodb-deadlocks.html didn't help me much.
I have the following questions:
1) What is the state of the database whenever I get the message ? Everything is frozen and the system expects from me to do something or my transaction has been already aborted and I just get informed about it ?
2) I'm using jdbc driver to connect to MySQL. Supposed my policy is to re-issue such failing transactions. Do I need to call connection.rollback() or MySQL has already done that for me ?
Thanks in advance
For the case of SERIALIZABLE I frequently get this error: "Deadlock found when trying to get lock; try restarting transaction at the client side".
Reading http://dev.mysql.com/doc/refman/5.6/en/innodb-deadlocks.html didn't help me much.
I have the following questions:
1) What is the state of the database whenever I get the message ? Everything is frozen and the system expects from me to do something or my transaction has been already aborted and I just get informed about it ?
2) I'm using jdbc driver to connect to MySQL. Supposed my policy is to re-issue such failing transactions. Do I need to call connection.rollback() or MySQL has already done that for me ?
Thanks in advance