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

MaxScale does not have time to open the file during rotation for a new binlog

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 23.08.6
    • binlogrouter
    • OS = Linux maxscale-binlog-router 4.18.0-448.el8.x86_64 #1 SMP Wed Jan 18 15:02:46 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
      MaxScale = 23.08.6
      MariaDB (slave) = 10.11.7
      mariadbd --print-defaults = attach mariadb.defaults
    • MXS-SPRINT-213, MXS-SPRINT-214

    Description

      MaxScale works in binlogrouter mode.
      Router = binlogrouter, Params in attach Params.json
      binlog_size=1G
      When rotating binlogs, maxscale does not have time to create a new file and make it writable. In this case, an error occurs when recording a portion of transactions (maxscale.log). It may be necessary to create the next binlog file in advance and keep it open. Don't wait until the current binlog file ends, but always have +1 for the next binlog file.
      At the same time, the slave mariadb cannot receive transactions that remained in the write buffer (for old closed binlog file) and were written to a new binlog file (mariadb_slave.log).
      Examples of searching for two transactions from the last two errors in the maria_slave.log file
      (last2errors.log)

      Attachments

        1. last2errors.log
          1 kB
        2. mariadb_slave.log
          7 kB
        3. mariadb.defaults
          3 kB
        4. maxscale.log
          12 kB
        5. Params.json
          1 kB

        Activity

          People

            nantti Niclas Antti
            dabbler Yuriy
            Votes:
            0 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.