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

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

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.1.3, 2.0.6
    • Component/s: MySQLMon
    • Labels:
      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

            Activity

              People

              • Assignee:
                Massimiliano Pinto Massimiliano Pinto
                Reporter:
                Massimiliano Pinto Massimiliano Pinto
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 0.5d
                  0.5d