← Back to team overview

enterprise-support team mailing list archive

[Bug 1554043] [NEW] main.log_tables-big unstable on loaded hosts

 

Public bug reported:

Copy of https://bugs.mysql.com/bug.php?id=80607:

[3 Mar 14:25] Laurynas Biveinis
Description:
main.log_tables-big                      w4 [ fail ]
        Test ended at 2016-03-02 10:44:16

CURRENT_TEST: main.log_tables-big
--- /mnt/workspace/mysql-5.7-param/BUILD_TYPE/release/Host/debian-jessie-64bit/mysql-test/r/log_tables-big.result	2016-03-01 19:44:59.428030231 +0300
+++ /mnt/workspace/mysql-5.7-param/BUILD_TYPE/release/Host/debian-jessie-64bit/build/mysql-test/var/4/log/log_tables-big.reject	2016-03-02 18:44:16.183238108 +0300
@@ -24,6 +24,7 @@
 0
 select if (query_time between '00:01:40' and '00:01:50', 'OK', 'WRONG') as qt, sql_text from mysql.slow_log;
 qt	sql_text
+WRONG	truncate table mysql.slow_log
 OK	select get_lock('bug27638', 101)
 select release_lock('bug27638');
 release_lock('bug27638')

The gist of the testcase is

truncate table mysql.slow_log;
select get_lock('bug27638', 2);
select if (query_time between '00:00:01' and '00:00:10', 'OK', 'WRONG') as qt, sql_text from mysql.slow_log;
... repeated with different get_lock timeouts ...

Two things can go wrong here, on a very loaded host:
1) truncate table may take >1 s to complete, getting logged into slow log table as in the output above
2) get_lock may take than timeout + 10 s to complete

How to repeat:
Testcase analysis. Not sure if MTR --repeat --parallel high on this testcase alone will help to repeat as the testcase spends most of the time sleeping.

Suggested fix:
1) add WHERE sql_text = "get_lock ... " to the mysql.slow_log selects
2) test only the lower time bound

** Affects: mysql-server
     Importance: Unknown
         Status: Unknown

** Affects: percona-server
     Importance: Low
     Assignee: Laurynas Biveinis (laurynas-biveinis)
         Status: In Progress

** Affects: percona-server/5.5
     Importance: Low
         Status: Won't Fix

** Affects: percona-server/5.6
     Importance: Low
     Assignee: Laurynas Biveinis (laurynas-biveinis)
         Status: In Progress

** Affects: percona-server/5.7
     Importance: Low
     Assignee: Laurynas Biveinis (laurynas-biveinis)
         Status: In Progress

** Also affects: percona-server/5.7
   Importance: Undecided
       Status: New

** Also affects: percona-server/5.5
   Importance: Undecided
       Status: New

** Also affects: percona-server/5.6
   Importance: Undecided
       Status: New

** Changed in: percona-server/5.5
       Status: New => Won't Fix

** Changed in: percona-server/5.6
       Status: New => In Progress

** Changed in: percona-server/5.6
   Importance: Undecided => Low

** Changed in: percona-server/5.6
     Assignee: (unassigned) => Laurynas Biveinis (laurynas-biveinis)

** Changed in: percona-server/5.5
   Importance: Undecided => Low

** Changed in: percona-server/5.7
       Status: New => In Progress

** Changed in: percona-server/5.7
   Importance: Undecided => Low

** Changed in: percona-server/5.7
     Assignee: (unassigned) => Laurynas Biveinis (laurynas-biveinis)

** Bug watch added: MySQL Bug System #80607
   http://bugs.mysql.com/bug.php?id=80607

** Also affects: mysql-server via
   http://bugs.mysql.com/bug.php?id=80607
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1554043

Title:
  main.log_tables-big unstable on loaded hosts

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1554043/+subscriptions


Follow ups