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

Failed rejoin can lead to a slave with read-only OFF

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.3
    • Fix Version/s: 2.2.6, 2.3.0
    • Component/s: mariadbmon
    • Labels:
      None

      Description

      Currently, any cluster operation which sets read-only=1, will disable read-only if a later stage fails. It seems the errors from Connector/C are not exactly correct, as the server may perform the operation anyways. In this case, monitor thinks that the operation failed and sets read-only=0, leading to a slave without read-only. This can be confusing for users. It seems MariaDB Backup has something to do with this as it also messes with the SQL-threads. Will need further investigation, but making the rejoin etc code smarter is probably a good step. Maybe, when getting an error the code should wait a second, reconnect, check status and try again.

        Attachments

          Activity

            People

            Assignee:
            esa.korhonen Esa Korhonen
            Reporter:
            esa.korhonen Esa Korhonen
            Votes:
            1 Vote for this issue
            Watchers:
            2 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.