Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.0.10
-
None
-
None
-
Debian Wheezy x64
Description
Hi.
From Tokutek documentation http://www.tokutek.com/wp-content/uploads/2013/10/mariadb-5.5.30-tokudb-7.1.0-users-guide.pdf:
4.2.5 tokudb_lock_timeout
....
A value of 0 disables lock waits
....
If tokudb_lock_timeout = 0, then lock waits should not happen. However with MariaDB 10.0.10 i've see, that if i request a table lock, the request refused with "#1205 - Lock wait timeout exceeded; try restarting transaction", so MariaDB now actually set lock timeout to zero milliseconds.
I think it will be better to match the behaviour with Tokutek version and disable lock waits, if tokudb_lock_timeout = 0.
Sincerely,
Alex.
Hi Alexander,
What do you expect to happen when lock waits are disabled?
From what I see, the Tokutek version behaves exactly the same way:
| @@version |
| 5.5.36-tokudb-7.1.5 |
| @@version_comment |
| MySQL Community Server (GPL) |
and it's the only reasonable way I can think of – 0 means that waiting is disabled, not the timeout; it doesn't mean that the statement will actually break the lock of another transaction. If waiting is disabled, the timeout happens right away.