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

bugzillaId-656: MySQL Monitor: claims that Master is available after master failure

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.0.0
    • 1.1.1
    • mariadbmon, Plugin
    • None
    • Linux

    Description

      This is imported from bugzilla item: http://bugs.mariadb.com/show_bug.cgi?id=656

      Description Vilho Raatikka 2014-12-18 15:16:42 UTC
      How to reproduce:
      1. start rwsplit with a master and optionally with slaves
      2. prevent connections to master by executing
      iptables -I INPUT -p tcp --dport 3000 -j REJECT --reject-with icmp-admin-prohibited
      3. read the message log:

      (..errors..)
      2014-12-18 17:09:30 Server 127.0.0.1:3000 lost the master status.
      2014-12-18 17:09:30 Info: A Master Server is now available: 127.0.0.1:3000
      2014-12-18 17:10:35 Info: A Master Server is now available: 127.0.0.1:3000

      Attachments

        Activity

          People

            markus makela markus makela
            tturenko Timofey Turenko
            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.