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

Setting event_scheduler to DISABLED causes bogus corruption errors

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 10.1, 10.2, 10.3, 10.4, 10.0
    • Fix Version/s: N/A
    • Component/s: Events, Variables
    • Labels:
      None

      Description

      When event_scheduler is set to DISABLED, event-related activities produce ER_EVENTS_DB_ERROR:

      MariaDB [test]> show events;
      ERROR 1577 (HY000): Cannot proceed because system tables used by Event Scheduler were found damaged at server start
      

      At the same time, trying to change the value at runtime produces a different error:

      MariaDB [test]> set global event_scheduler=on;
      ERROR 1290 (HY000): The MariaDB server is running with the --event-scheduler=DISABLED or --skip-grant-tables option so it cannot execute this statement
      

      This is confusing, especially when it comes to investigation of real-life problems.
      If we can't distinguish real corruption from the user setting, which is probably the case, maybe it would be best to disallow user to set the option to DISABLED and keep it an internal-only value.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              wlad Vladislav Vaintroub
              Reporter:
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: