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

1.4.1: ReadWrite Split on Master-Master setup doesn't chose master, logs "RUNNING MASTER" error message instead (related to MXS-511?)

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.4.1
    • 2.0.0
    • readwritesplit
    • Debian Wheezy, MariaDB 10.0.19 Master-Master-Replication

    Description

      When moving a client's setup from MMM script based setup to MaxScale I ran into the same problem that is described in MXS-511 with the difference that this setup isn't a Galera cluster but a master-master replication. So the obvious difference is that the monitor plugin used is 'mmmon'.
      I verified that both nodes are indeed synced.

      Configs and logs can be provided if needed.

      Attachments

        Activity

          People

            markus makela markus makela
            whocares Stefan Rubner
            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.