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

Mariadbmon loses locks without reporting a broken connection

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 2.5.19, 6.4.5, 22.08.4, 23.02
    • 2.5.19
    • Monitor
    • None
    • RHEL 7
    • MXS-SPRINT-192, MXS-SPRINT-193

    Description

      The monitor connections unconditionally enable MYSQL_OPT_RECONNECT which can hide the loss of cooperative monitoring locks. Unfortunately the failover requires this option so it cannot outright be disabled.

      Original description:
      Stop slave on slave server changes master's status on MaxScale. 

      Server changed state: xxx1p[192.168.254.52:3306]: new_master. [Slave, Running] -> [Master, Running]

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MXS-4511 master status change when run stop slave

          • Major - Major loss of function.
          • Closed

          Activity

            People

              esa.korhonen Esa Korhonen
              allen.lee@mariadb.com Allen Lee (Inactive)
              Votes:
              1 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.