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

Running RESET MASTER TO n with too big n breaks binary logging

    XMLWordPrintable

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 10.1.6
    • 10.1(EOL)
    • Replication
    • None

    Description

      MariaDB [test]> show binary logs;
      +------------------+-----------+
      | Log_name         | File_size |
      +------------------+-----------+
      | mysql-bin.000001 |       312 |
      +------------------+-----------+
      1 row in set (0.00 sec)
       
      MariaDB [test]> reset master to 2147483647;
      Query OK, 0 rows affected (0.36 sec)
       
      MariaDB [test]> show binary logs;
      +----------------------+-----------+
      | Log_name             | File_size |
      +----------------------+-----------+
      | mysql-bin.2147483647 |       316 |
      +----------------------+-----------+
      1 row in set (0.00 sec)
       
      # So far, so good...

      MariaDB [test]> reset master to 2147483648;
      ERROR 1098 (HY000): Can't generate a unique log-filename mysql-bin.(1-999)
       
      MariaDB [test]> show binary logs;
      Empty set (0.00 sec)
       
      MariaDB [test]> reset master to 1;
      ERROR 1373 (HY000): Target log not found in binlog index
      MariaDB [test]> reset master;
      ERROR 1373 (HY000): Target log not found in binlog index
      MariaDB [test]> create table t1 (i int);
      ERROR 3 (HY000): Error writing file 'UNOPENED' (Errcode: 9 "Bad file descriptor")

      Attachments

        Issue Links

          Activity

            People

              monty Michael Widenius
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.