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

bugzillaId-589: detect if MAXSCALE_SCHEMA.HEARTBEAT table is not replicated

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.0.1
    • 1.3.0
    • Core, mariadbmon
    • None
    • Linux

    Description

      This item is imported from bugzilla http://bugs.mariadb.com/show_bug.cgi?id=589

      Vilho Raatikka 2014-10-22 12:40:44 UTC
      If replication lag is also monitored, monitor user must have enough permissions to create schema, insert and read rows from its tables. That's because MaxScale creates MAXSCALE_SCHEMA and HEARTBEAT table in it.

      [MySQL Monitor]
      type=monitor
      module=mysqlmon
      servers=server1,server2,server3
      user=maxuser
      passwd=maxpwd
      # 
      # options for mysql_monitor only
      #
      detect_replication_lag=1
       

      MySQL replication setup may limit what is replicated. If MAXSCALE_SCHEMA.HEARTBEAT isn't replicated replication lag can't be resolved for any of the slaves. As a consequence, all queries are routed to master.

      What is asked is detection of this situation and such a log write to error and trace log that user recognizes the case.

      Attachments

        Activity

          People

            markus makela markus makela
            tturenko Timofey Turenko
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.