5.5.13 sys_vars.slow_launch_time_func fails w/ TPS=4

Bug #780487 reported by Valentine Gostev on 2011-05-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Rodrigo Gadea

Bug Description

sys_vars.slow_launch_time_func [ fail ]
        Test ended at 2011-05-10 16:45:28

CURRENT_TEST: sys_vars.slow_launch_time_func
--- /root/HEAP/mysql-test/suite/sys_vars/r/slow_launch_time_func.result 2011-05-06 18:25:36.760325000 +0300
+++ /root/HEAP/mysql-test/suite/sys_vars/r/slow_launch_time_func.reject 2011-05-10 15:45:28.203986407 +0300
@@ -6,6 +6,14 @@
 ** Connecting conn1 using username 'root' **
+ERROR: Subtest FN_DYNVARS_124_01 failed
+A new connect should be counted as 'slow_launch_thread' if
+SELECT @@GLOBAL.slow_launch_time;
+Number of slow_launch_threads before new connect: 0
+Number of slow_launch_threads after new connect: 0
 ** Switch to connection default and disconnect conn1 **
 SET @@GLOBAL.slow_launch_time= 1000;

mysqltest: Result content mismatch

Changed in percona-projects-qa:
milestone: none → 5.5.13
Changed in percona-projects-qa:
assignee: nobody → Laurynas Biveinis (laurynas-biveinis)
Changed in percona-projects-qa:
status: New → Triaged
importance: Undecided → High
Changed in percona-projects-qa:
status: Triaged → In Progress
Changed in percona-projects-qa:
status: In Progress → Fix Committed

slow_launch_time is meaningless for thread pool, as no new threads are created to handle incoming requests. So for the thread pool slow_launch_time is adjusted to mean the upper bound for time between thread pool receiving request and a thread starting working on that request. The docs/release notes have to be adjusted for this.

Changed in percona-projects-qa:
status: Fix Committed → In Progress
importance: High → Medium
assignee: Laurynas Biveinis (laurynas-biveinis) → Rodrigo Gadea (rodrigo-gadea-percona)
Changed in percona-projects-qa:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers