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

MySQL monitor "detect_replication_lag=true" doesn't work with "mysql51_replication=true"

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 2.0.6, 2.1.3
    • mariadbmon
    • None

    Description

      The call to function set_master_heartbeat requires both arguments handle and root_master not to be null for being able to succeed.

      but handle->master is always null and there's no chance for set_master_heartbeat to create the database maxscale_schema and table replication_heartbeat.

      it seems an intrinsic bug of MaxScale not being able to cope detect_replication_lag=true when mysql51_replication=true.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MXS-1260 MaxAdmin show service missing stats with MariaDB 5.1 MySQLBackend

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MXS-1272 MySQL Monitor with a Replication Cluster using MariaDB 5.1 does not report correctly Master details

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              Massimiliano Pinto Massimiliano Pinto (Inactive)
              Massimiliano Pinto Massimiliano Pinto (Inactive)
              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.