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

slave_connections_needed_for_purge prevents independent machine from purging binary logs

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Critical
    • Resolution: Unresolved
    • None
    • N/A
    • Replication
    • None
    • Q3/2026 Server Maintenance

    Description

      With variable slave_connections_needed_for_purge, a primary machine needs to check replicas before purging binary logs. If a replica is not there and the machine is a standalone machine, it just does not purge the binary logs and ignores log_expire_days variable and binary logs fills the disk space.
      Binary log purge is not happening due to the default behavior of `slave_connections_needed_for_purge` to `1` on a standalone server.

      If the MariaDB is able to determine whether we are a standalone installation and if so set default value slave_connections_needed_for_purge to 0.
      The default of 1 is not appropriate unless we are in fact part of a replica group.

      Attachments

        Issue Links

          Activity

            People

              bnestere Brandon Nesterenko
              rohit.kumar Rohit Kumar
              Votes:
              1 Vote for this issue
              Watchers:
              9 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.