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

Too many monitor events are triggered

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.2.2
    • Component/s: mariadbmon
    • Labels:
      None

      Description

      When the mariadbmon is configured with ignore_external_masters, the monitor triggers a new_master event when the Slave of External Server status gets removed. This also happens when a slave is promoted as a master and the slave status is remove. These events should not happen as they are not truly functional changes in state.

      2018-02-02 23:19:14   notice : Server changed state: server3[127.0.0.1:3002]: new_master. [Slave, Running] -> [Master, Slave, Running]
      2018-02-02 23:19:14   notice : [mariadbmon] A Master Server is now available: 127.0.0.1:3002
      2018-02-02 23:19:16   notice : Server changed state: server3[127.0.0.1:3002]: new_master. [Master, Slave, Running] -> [Master, Running]
      2018-02-02 23:19:16   notice : [mariadbmon] A Master Server is now available: 127.0.0.1:3002
      

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: