Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-1586

Mysqlmon switchover does not immediately detect bad new master

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.2
    • Component/s: mariadbmon
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-50, MXS-SPRINT-51

      Description

      If a master switchover is initiated and the specified server cannot be used as master, that it is not actively detected but will become apparent only as a side-effect of the attempt failing due to a timeout.

      The test mysqlmon_switchover_bad_master tests this and the test reports:

      Trying to do manual switchover to server4
      {
          "errors": [
              {
                  "detail": "MASTER_GTID_WAIT() timed out on slave 'server4'."
              }
          ]
      }
      

      So, the switchover fails, which is the expected outcome, but the fact that the server cannot serve as master should be detected immediately.

        Attachments

          Activity

            People

            Assignee:
            esa.korhonen Esa Korhonen
            Reporter:
            johan.wikman Johan Wikman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: