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

The DISABLE ON SLAVE option sets the status SLAVESIDE_DISABLED on master and slaves EVENTS

    XMLWordPrintable

    Details

      Description

      The DISABLE ON SLAVE option sets the status SLAVESIDE_DISABLED on master and slaves EVENTS

      This appears to be a bug that has been around for some time and/or a leftover from the past with a misleading status for an EVENT on a master node.

      I can't think of a case were changing an EVENT to DISABLE ON SLAVE would be useful, since by default CREATE EVENT sets the status on the slaves to SLAVESIDE_DISABLED.

      "DISABLE ON SLAVE" used with CREATE or ALTER EVENT should either:

      A) NOT change the EVENT status on the master node to SLAVESIDE_DISABLED and keeping current ENABLED or DISABLED status on master. Or act like the DISABLE option and keep the event status on the slaves to SLAVESIDE_DISABLED.

      Or

      B) Remove the DISABLE ON SLAVE option altogether from CREATE or ALTER EVENT. DISABLE can be used instead. Having the status SLAVESIDE_DISABLED on an EVENT on the master node is misleading.

      Also see MDEV-12284

        Attachments

          Activity

            People

            Assignee:
            serg Sergei Golubchik
            Reporter:
            martin.reinhardt@mariadb.com Martin Reinhardt
            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.