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

Galera monitor: Minimum cluster size and/or refuse two cluster IDS in 1 cluster

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.1.0
    • galeramon
    • None
    • 2017-26, 2017-27

    Description

      I think 2 extra features in the Galera monitor module would be a good addition to MaxScale.

      If we have a 3 node galera cluster and somebody accidently bootstrap each one (or 2) of them, MaxScale would currently send traffic to all nodes allthough they are not in a cluster together.

      I think there are 2 ways to avoid this in the MaxScale monitor, option 1 is easy and option 2 is elegant.
      1: Config parameter with the minimum cluster size. If any node is up but the minimum cluster size is too low, consider the node down.

      2a: If there are several cluster identifiers present in the list of servers MaxScale knows about, only consider the servers with cluster identifier that occurs at least 1 time more then the other identifier(s)
      2b: If there are several cluster identifiers present in the servers MaxScale knows about do not consider any of the nodes up

      Attachments

        Activity

          People

            Massimiliano Pinto Massimiliano Pinto (Inactive)
            michaeldg Michaël de groot
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.