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

Document innodb-lock-schedule-algorithm details

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • N/A
    • N/A
    • Documentation
    • None

    Description

      Ian Gilfillan Can you document that innodb-lock-schedule-algorithm is read-only variables (i.e. it can't be changed dynamically) and that VATS method is not supported on Galera.

      Here what documentation should mention:

      10.1, default is FCFS and InnoDB will refuse to start if VATS is used with galera.
      >=10.2 default is VATS and in galera it will be changed to FCFS.

      Attachments

        Issue Links

          Activity

            greenman Ian Gilfillan created issue -
            greenman Ian Gilfillan made changes -
            Field Original Value New Value
            greenman Ian Gilfillan added a comment -

            jplindst will setting innodb-lock-schedule-algorithm details to FCFS be sufficient for people currently running 10.2 (before 10.2.12 is released), or should people avoid upgrading altogether if running Galera?

            greenman Ian Gilfillan added a comment - jplindst will setting innodb-lock-schedule-algorithm details to FCFS be sufficient for people currently running 10.2 (before 10.2.12 is released), or should people avoid upgrading altogether if running Galera?
            elenst Elena Stepanova made changes -
            Fix Version/s N/A [ 14700 ]
            Affects Version/s N/A [ 14700 ]
            danblack Daniel Black added a comment -

            in https://github.com/MariaDB/server/commit/da3a3a68df34c7fef387ce890d3925166edeef2c#diff-bbb9322fe6d0355bb459fe6df3a5126c it can't be set to vats and will fail in wsrep_on_check and revert to FCFS with warning.

            danblack Daniel Black added a comment - in https://github.com/MariaDB/server/commit/da3a3a68df34c7fef387ce890d3925166edeef2c#diff-bbb9322fe6d0355bb459fe6df3a5126c it can't be set to vats and will fail in wsrep_on_check and revert to FCFS with warning.
            greenman Ian Gilfillan added a comment -

            Thanks danblack I think this is documented in https://mariadb.com/kb/en/library/xtradbinnodb-server-system-variables/#innodb_lock_schedule_algorithm (have added that it produces a warning), but am waiting for clarity from jplindst or anyone else on running 10.2 Galera before this fix.

            greenman Ian Gilfillan added a comment - Thanks danblack I think this is documented in https://mariadb.com/kb/en/library/xtradbinnodb-server-system-variables/#innodb_lock_schedule_algorithm (have added that it produces a warning), but am waiting for clarity from jplindst or anyone else on running 10.2 Galera before this fix.

            greenman Yes setting innodb-lock-schedule-algorithm=FCFS is sufficient.

            jplindst Jan Lindström (Inactive) added a comment - greenman Yes setting innodb-lock-schedule-algorithm=FCFS is sufficient.
            greenman Ian Gilfillan added a comment - Noted in the docs: https://mariadb.com/kb/en/library/upgrading-from-mariadb-101-to-mariadb-102/#galera
            greenman Ian Gilfillan made changes -
            Resolution Not a Bug [ 6 ]
            Status Open [ 1 ] Closed [ 6 ]
            greenman Ian Gilfillan added a comment -

            Accidentally changed to "not a bug" when closing

            greenman Ian Gilfillan added a comment - Accidentally changed to "not a bug" when closing
            greenman Ian Gilfillan made changes -
            Resolution Not a Bug [ 6 ]
            Status Closed [ 6 ] Stalled [ 10000 ]
            greenman Ian Gilfillan made changes -
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 84629 ] MariaDB v4 [ 153457 ]

            People

              greenman Ian Gilfillan
              greenman Ian Gilfillan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.