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

heartbeat replication don't support multimaster

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.3.2
    • mariadbmon
    • None
    • MXS-SPRINT-67, MXS-SPRINT-68, MXS-SPRINT-69, MXS-SPRINT-70

    Description

      Maxscale configured with

      Service
      router=readwritesplit
      master_accept_reads=true
      max_slave_replication_lag
       
       
      Monitor
      module=mysqlmon
      multimaster=true
       
      detect_replication_lag=true
      

      Setup
      Master1 - Master 2 - Salve

      2018-01-08 14:42:40   notice : Server changed state: db-node1[x.x.x.x1:3306]: new_master. [Running] -> [Master, Running]
      2018-01-08 14:42:40   notice : Server changed state: db-node2[x.x.x.2:3306]: new_master. [Running] -> [Master, Running]
      2018-01-08 14:42:40   notice : Server changed state: db-node3[X.X.X.3:3306]: new_slave. [Running] -> [Slave, Running]
      

      Heartbeat tables will only be filled on Master1 (x.x.x.1) and Slave (x.x.x.3)

      possible root cause:

      heartbeat did not recognize master as a slave

       if ((!SERVER_IN_MAINT(ptr->server)) && SERVER_IS_RUNNING(ptr->server))
                      {
                          if (ptr->server->node_id != root_master->server->node_id &&
                              (SERVER_IS_SLAVE(ptr->server) ||
                               SERVER_IS_RELAY_SERVER(ptr->server)))
      

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            Richard Richard Stracke
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.