Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6226

tokudb_lock_timeout 0 is not working as expected in MariaDB compared to Tokutek's version

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: 10.0.10
    • Fix Version/s: None
    • Component/s: None
    • Environment:
      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.

        Attachments

          Activity

            People

            • Assignee:
              elenst Elena Stepanova
              Reporter:
              Profforg Alexander Loginov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: