Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-27919

mariabackup --log-copy-interval is measured in milliseconds in 10.5 and in microseconds in 10.6

    XMLWordPrintable

    Details

      Description

      Hi, all MariaBackup developers.

      We have two MariaDB clusters, which both version 10.0.x

      And recently upgraded from 10.0.x to 10.6.2
      But I found that the log ">> log scanned up to (...)" print too fast, overwhelming the stdout/stderr. (the log file size is occupied by several gigabytes)

      But as I tested, when I upgraded from 10.0.x to 10.5.x, the log ">> log scanned up to (...)" is not so overwhelming. (the log file size is occupied by several megabytes)

      FYI, Recovered from the same database backup.

      It sounds like a bug in mariabackup, since the --log-copy-interval (default is 1000ms) can't control the log output frequency.

      # 10.5 MariaBackup
      # One log per second
      [00] 2022-02-14 17:50:25 >> log scanned up to (46200984432003)
      [00] 2022-02-14 17:50:26 >> log scanned up to (46200984454330)
      [00] 2022-02-14 17:50:27 >> log scanned up to (46200984469322)
      [00] 2022-02-14 17:50:28 >> log scanned up to (46200984491853)
      [00] 2022-02-14 17:50:29 >> log scanned up to (46200984529292)
      [00] 2022-02-14 17:50:30 >> log scanned up to (46200984561329)
       
      # 10.6 MariaBackup
      # --log-copy-interval=1000 is not working for 10.6
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221905582)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221906153)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221906805)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221906805)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221906805)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221907586)
      [00] 2022-02-22 17:11:48 >> log scanned up to (46276221908255)
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              vlad.lesin Vladislav Lesin
              Reporter:
              hcooper Harvey Cooper
              Votes:
              1 Vote for this issue
              Watchers:
              7 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.