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

add sticky_master option to MySQL Monitor

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.1.0
    • Component/s: mariadbmon
    • Labels:
      None
    • Environment:
      CentOS Linux release 7.3.1611
      maxscale-2.0.1-2.x86_64

      Description

      There is three servers. I setup it with mariadb replication and maxscale R/W splitting router.

      server2 -> server3 -> server1

      The master is server2. The server3 is intermediate database. The server1 is a slave.
      If the server2 was failed, writing queries failover to server3.
      If the server2 came back, writing queries failback to server2.
      And It will occur replication error on the server3.
      I don't want this behavior.
      I want option to fix the master node.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            g980 sava
            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.