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

Node wrongly in Maintenance, Running when the node is actually Down

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.3.19
    • 6.0.0
    • galeramon
    • None
    • Centos 7.6
    • MXS-SPRINT-128, MXS-SPRINT-129

    Description

      When setting backend Galera-node to maintenance-mode and after that stopping that node, MaxScale does not detect that the node has went down and showing wrongly Maintenance, Running. It should be Maintenance, Down.

      There are zero lines on MaxScale log when node on maintenance-mode is stopped.

      This kills the logic of our in-house solution where we use output of command maxctrl list servers to see status of the running Galera Cluster.

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            mihaQ MikaH
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 1d
                1d

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.