Threads_running becomes very large
Bug #1040108 reported by
johan
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
High
|
Teemu Ollakka |
Bug Description
Sometimes, after node recovery is most common the Threads_running becomes set to 2^64-1.
I will try and create a reproducable test case.
-J
Related branches
Changed in codership-mysql: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
btw 2^64-1 should be 2^32
I use Haproxy to loadbalance across 4 servers and sysbench to drive load:
sysbench --test=oltp --mysql- table-engine= innodb --oltp- table-size= 1000000 --mysql-user=johan --mysql- password= 123johan --mysql- host=127. 0.0.1 --mysql-port=33306 --num-threads=64 --max-time=36000 --max-requests=0 run
on one node do:
service mysql restart
show global status like 'threads_running';
mysql> show global status like 'threads_running'; ------- ----+-- ------- ---+ ------- ----+-- ------- ---+ ------- ----+-- ------- ---+
+------
| Variable_name | Value |
+------
| Threads_running | 4294967260 |
+------
1 row in set (0.00 sec)
This value is the same across all servers.'