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

default value for sync_binlog should be the safer value 1 instead of 0

    XMLWordPrintable

Details

    • New Feature
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • Replication, Server
    • None

    Description

      The default variable for sync_binlog is 0 for MariaDB, where Oracle changed it to 1 starting with 5.7.7. I think we should also change the default to 1, as running a master with sync_binlog=0 is risky - any crash of server or mysqld will create inconsistent slaves 99% of the time.

      Attachments

        1. group_commit_benchmark.png
          group_commit_benchmark.png
          75 kB
        2. innodb_binlog_on_ssd.png
          innodb_binlog_on_ssd.png
          45 kB
        3. innodb_binlog.png
          innodb_binlog.png
          49 kB
        4. sysbench.pdf
          21 kB

        Issue Links

          is blocked by

          New Feature - A new feature of the product, which has yet to be developed. MDEV-18959 Engine transaction recovery through persistent binlog

          • Major - Major loss of function.
          • Stalled

          Technical task - A technical task. MDEV-24386 MDEV-16589 benchmark & analysis

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-34705 Storing binlog in InnoDB

          • Major - Major loss of function.
          • In Progress

          Activity

            People

              Elkin Andrei Elkin
              rpizzi Rick Pizzi (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.