Uploaded image for project: 'Percona Server for MySQL'
  1. Percona Server for MySQL
  2. PS-3667

LP #1676740: Test innodb.percona_log_arch_expire_sec is unstable

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None

      Description

      **Reported in Launchpad by Laurynas Biveinis last update 16-06-2017 06:37:06

      On 5.6 trunk:

      innodb.percona_log_arch_expire_sec w1 [ fail ]
      Test ended at 2017-03-24 10:00:06

      CURRENT_TEST: innodb.percona_log_arch_expire_sec
      mysqltest: At line 23: Test failed. Archived logs have nod been purged.

      The result from queries just before the failure was:
      call mtr.add_suppression("InnoDB: Resizing redo log");
      call mtr.add_suppression("InnoDB: Starting to delete and rewrite log files");
      call mtr.add_suppression("InnoDB: New log files created");
      call mtr.add_suppression("InnoDB: The log sequence numbers [0-9]+ and [0-9]+ in ibdata files do not match the log sequence number [0-9]+ in the ib_logfiles");
      drop table if exists t;
      create table t (a int not null) ENGINE=InnoDB;
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),(13);
      insert into t (a) select t1.a from t t1, t t2, t t3 LIMIT 40000;
      SET @save_log_arch_expire_sec = @@innodb_log_arch_expire_sec;
      SET GLOBAL innodb_log_arch_expire_sec = 1;
      insert into t (a) select t1.a from t t1, t t2, t t3 LIMIT 40000;
      insert into t (a) select t1.a from t t1, t t2, t t3 LIMIT 40000;
      SELECT sleep(4);
      sleep(4)
      0
      safe_process[16218]: Child process: 16219, exit: 1

      The cause is that the expired log purge is a background process, and there is no synchronisation.

        Smart Checklist

          Attachments

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              lpjirasync lpjirasync (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: