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

Read with max_slave_connections=0 fails with master_failure_mode=fail_on_write

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 6.4.15, 22.08.12, 23.02.9, 23.08.5, 24.02.1
    • N/A
    • None
    • MXS-SPRINT-208

    Description

      If the current master fails and readwritesplit is configued in the following way, the read will fail.

      [ReadWriteSplit]
      type=service
      router=readwritesplit
      max_slave_connections=0
      master_reconnection=true
      master_failure_mode=fail_on_write
      

      This problem is related to MXS-5085 where a read after a switchover did not correctly select the new master. When MXS-5085 is fixed, this problem could be solved by temporarily allowing a slave connection to be created if a valid root master is not found and the router is configured with max_slave_connections=0. However, this will cause an extra slave connection to remain in use even once a new master connection is created.

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              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.