Bug #39937 | Sporadic failures of main.status around results containing the word "thread" | ||
---|---|---|---|
Submitted: | 8 Oct 2008 17:30 | Modified: | 5 Feb 2009 13:03 |
Reporter: | Matthias Leich | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Tests: Server | Severity: | S3 (Non-critical) |
Version: | 6.0+ | OS: | Any |
Assigned to: | Horst Hunger | CPU Architecture: | Any |
Tags: | pushbuild, sporadic, test failure |
[8 Oct 2008 17:30]
Matthias Leich
[2 Feb 2009 9:13]
Lars Thalmann
See also BUG#39857
[3 Feb 2009 13:31]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/65003 3007 Horst Hunger 2009-02-03 Fix for bug#39937: Set the disconnect_timeout to 30 seconds to have more time in case of lower performance and specified a weaker condition as sometime also a "Quit" is counted as query.
[3 Feb 2009 14:47]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/65022 2768 Horst Hunger 2009-02-03 Revised fix for bug#39937: Set the disconnect_timeout to 30 seconds to have more time in case of lower performance and specified a weaker condition as sometime also a "Quit" is counted as query.
[4 Feb 2009 10:18]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/65109 2768 Horst Hunger 2009-02-04 New fix for bug#39937: I inserted a waiting until the server has gone and increased the disconnection_timeout to 30 seconds to give the server more time to change the status variables in case of low perfoemance. I tried to change as less as possible in the test, means no changes in the result.
[4 Feb 2009 19:00]
Davi Arnaut
Duplicate of Bug#37481?