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

Stopping IO thread on relay master causes it to be promoted as master

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.13
    • Fix Version/s: 2.1.14
    • Component/s: mariadbmon
    • Labels:
      None

      Description

      With a four server setup consisting of two master-slave pairs, A→B and C→D where A and C are masters, configuring C to replicate from A will form a multi-tiered replication topology (i.e. C will be a relay master).

      "Before stopping IO thread"

      Servers.
      -------------------+-----------------+-------+-------------+--------------------
      Server             | Address         | Port  | Connections | Status
      -------------------+-----------------+-------+-------------+--------------------
      server1            | 127.0.0.1       |  3000 |           0 | Master, Running
      server2            | 127.0.0.1       |  3001 |           0 | Slave, Running
      server3            | 127.0.0.1       |  3002 |           0 | Relay Master, Slave, Running
      server4            | 127.0.0.1       |  3003 |           0 | Slave, Running
      -------------------+-----------------+-------+-------------+--------------------
      

      When the IO thread on C (server3) is stopped, it will be "promoted" as a master server.

      "After stopping IO thread"

      Servers.
      -------------------+-----------------+-------+-------------+--------------------
      Server             | Address         | Port  | Connections | Status
      -------------------+-----------------+-------+-------------+--------------------
      server1            | 127.0.0.1       |  3000 |           0 | Master, Running
      server2            | 127.0.0.1       |  3001 |           0 | Slave, Running
      server3            | 127.0.0.1       |  3002 |           0 | Master, Running
      server4            | 127.0.0.1       |  3003 |           0 | Slave, Running
      -------------------+-----------------+-------+-------------+--------------------
      

      If C disconnects from A, it should not be treated as a master server.

        Attachments

          Activity

            People

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