Uploaded image for project: 'Percona Toolkit'
  1. Percona Toolkit
  2. PT-1235

LP #1350478: incorrect command line example when innodb_lock_wait_timeout error occurs

    XMLWordPrintable

    Details

      Description

      **Reported in Launchpad by Geoffrey Hoffman last update 15-08-2014 14:17:42

      I tried to run

      pt-online-schema-change --alter "ENGINE=InnoDB" D=dbname,t=tablename

      but it gave:

      Error setting innodb_lock_wait_timeout: DBD::mysql::db do failed: Variable 'innodb_lock_wait_timeout' is a read only variable [for Statement "SET SESSION innodb_lock_wait_timeout=1"]. The current value for innodb_lock_wait_timeout is 50. If the variable is read only (not dynamic), specify --set-vars innodb_lock_wait_timeout=50 to avoid this warning, else manually set the variable and restart MySQL.

      Notice that this part:

      SET SESSION innodb_lock_wait_timeout=1

      is correct, while this part:

      --set-vars innodb_lock_wait_timeout=50

      is incorrect. It appears to be putting "50" into the command line example of what I need to do, instead of "1".

      That should say:

      --set-vars innodb_lock_wait_timeout=1

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            lpjirasync lpjirasync (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Smart Checklist