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

Maxscale configuration needed for master<->master replication

Details

    Description

      We have installed Mariadb 10.2.12 on two servers A and B then setup Master<>Master replication so we need to know the maxscale configuration of this Master<>Master setup.

      FYI, Server A is on ReadWrite mode and Server B is in ReadOnly mode.

      Our intention is to pass write operations to Server A and read operations to Server B only. Please let me know the configuration of Maxscale about this replication setup.

      Thanks,
      Venkat Beru

      Attachments

        Activity

          markus makela markus makela added a comment -

          As this is not a technical task, I will close this issue.

          Please took at the MaxScale tutorials for examples on how to configure your cluster. If you would like to receive help with your configuration or setup, I would recommend contacting the MariaDB Corporation who offer such assistance.

          markus makela markus makela added a comment - As this is not a technical task, I will close this issue. Please took at the MaxScale tutorials for examples on how to configure your cluster. If you would like to receive help with your configuration or setup, I would recommend contacting the MariaDB Corporation who offer such assistance.

          Thank you Markus makela. Just would like to get a confirmation,is it possible to perform switch over and failover in MASTER<->MASTER replication configuration by using Maxscale 2.2.5 or not?

          Thanks,
          Venkat Beru

          venkatberu Venkatarao Beru added a comment - Thank you Markus makela. Just would like to get a confirmation,is it possible to perform switch over and failover in MASTER<->MASTER replication configuration by using Maxscale 2.2.5 or not? Thanks, Venkat Beru

          Waiting for your updates/suggestions about my last comment...

          Thanks,
          Venkat Beru

          venkatberu Venkatarao Beru added a comment - Waiting for your updates/suggestions about my last comment... Thanks, Venkat Beru
          markus makela markus makela added a comment -

          The MariaDBMon failover mechanism does not support multi-master configurations (mainly because it is redundant if all connections go though MaxScale). The recommended approach would be to instead use normal Master→Slave replication and allow MaxScale to control who is the master.

          Read the section on automated failover in the MaxScale documentation, it should give you insight into what is possible with MaxScale. There is also a MaxScale tutorial on automatic failover, I'd recommend reading it for a practical viewpoint to automated failover.

          markus makela markus makela added a comment - The MariaDBMon failover mechanism does not support multi-master configurations (mainly because it is redundant if all connections go though MaxScale). The recommended approach would be to instead use normal Master→Slave replication and allow MaxScale to control who is the master. Read the section on automated failover in the MaxScale documentation, it should give you insight into what is possible with MaxScale. There is also a MaxScale tutorial on automatic failover , I'd recommend reading it for a practical viewpoint to automated failover.

          Thank you Makela for your confirmation.

          venkatberu Venkatarao Beru added a comment - Thank you Makela for your confirmation.

          People

            Unassigned Unassigned
            venkatberu Venkatarao Beru
            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.