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

max_slave_replication_lag should be in mysqlmon, not readwritesplit

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Do
    • None
    • N/A
    • N/A
    • None

    Description

      The MySQL monitor should handle slave servers that are too much behind the master. By removing the Slave status from any server that lags too far behind, the same functionality is achieved that is currently in the readwritesplit.

      This also allows for some rudimentary IO health checks by checking that the insert into the heartbeat table can be done. If it can't be done then the master is not fully functional.

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              markus makela markus makela
              Votes:
              1 Vote for this issue
              Watchers:
              3 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.