| Bug #23921 | random failure of user_limits.test | ||
|---|---|---|---|
| Submitted: | 3 Nov 2006 9:39 | Modified: | 18 Aug 19:16 |
| Reporter: | Timothy Smith | ||
| Status: | Closed | ||
| Category: | Server: Tests | Severity: | S3 (Non-critical) |
| Version: | 5.1, 6.0 | OS: | Any (*) |
| Assigned to: | Tatjana A. Nuernberg | Target Version: | 6.0 |
| Tags: | pushbuild, test failure, sporadic | ||
| Triage: | D3 (Medium) | ||
[3 Nov 2006 9:39]
Timothy Smith
[9 May 2007 11:16]
Magnus Svensson
This test has not failed one single time this year, see https://intranet.mysql.com/secure/pushbuild/xref.pl?startdate=&enddate=&dir=&plat=&testtyp e=&testname=user_limits&testtext=&limit=50 Closing the bug report.
[16 Dec 2007 10:51]
Konstantin Osipov
The bug does not appear to be fixed in 6.0. The test was disabled for a long time in 6.0, today I tried to enable it and got a random failure again: main.user_limits [ fail ] mysqltest: At line 108: query 'connect muc3, localhost, mysqltest_1,,' failed: 1226: User 'mysqltest_1' has exceeded the 'max_user_connections' resource (current value: 2) The result from queries just before the failure was: < snip > select * from t1; i select * from t1; i connect(localhost,mysqltest_1,,test,MYSQL_PORT,MYSQL_SOCK); ERROR 42000: User 'mysqltest_1' has exceeded the 'max_connections_per_hour' resource (current value: 2) select * from t1; i connect(localhost,mysqltest_1,,test,MYSQL_PORT,MYSQL_SOCK); ERROR 42000: User 'mysqltest_1' has exceeded the 'max_connections_per_hour' resource (current value: 2) drop user mysqltest_1@localhost; flush privileges; grant usage on *.* to mysqltest_1@localhost with max_user_connections 2; flush user_resources; select * from t1; i select * from t1; i connect(localhost,mysqltest_1,,test,MYSQL_PORT,MYSQL_SOCK); ERROR 42000: User 'mysqltest_1' has exceeded the 'max_user_connections' resource (current value: 2) More results from queries before failure can be found in /tmp/var-n_mix-100/log/user_limits.log Stopping All Servers Restoring snapshot of databases Resuming Tests https://intranet.mysql.com/secure/pushbuild/getlog.pl?dir=mysql-6.0-runtime&entry=kosipov@ bodhi.none-20071215231512&name=test_n_mix&plat=sol10-sparc-a
[15 Jun 16:49]
Tatjana A. Nuernberg
Seeing this for ER_TOO_MANY_USER_CONNECTIONS and ER_USER_LIMIT_REACHED; this is always caught on the first retry in my tests. catching race @ line 108 on attempt 1 for error #1226:42000 (ER_USER_LIMIT_REACHED) (per-user max-user-connections/max-connections-per-hour/max-questions/max-updates, of which the latter two are irrelevant for our case and the 2nd takes intent to trigger) catching race @ line 143 on attempt 1 for error #1203:42000 (ER_TOO_MANY_USER_CONNECTIONS) (global max-user-connections) http://dev.mysql.com/doc/refman/5.1/en/user-resources.html cf. sql/sql_connect.cc
[15 Jul 13:45]
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/49751 2662 Tatiana A. Nurnberg 2008-07-15 Bug#23921: random failure of user_limits.test mysqltest disconnect/connect-combo could be so quick that connect would hit the server before it had processed the disconnect. Since that resulted in one more concurrent connection than we meant to have, global or per-user max-user-connections could be exceeded. This could lead to "random" failures in tests that set those limits.
[21 Jul 11:58]
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/50105 2668 Tatiana A. Nurnberg 2008-07-21 [merge] Bug#23921: random failure of user_limits.test mysqltest disconnect/connect-combo could be so quick that connect would hit the server before it had processed the disconnect. Since that resulted in one more concurrent connection than we meant to have, global or per-user max-user-connections could be exceeded. This could lead to "random" failures in tests that set those limits.
[21 Jul 12:26]
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/50109 2731 Tatiana A. Nurnberg 2008-07-21 [merge] Bug#23921: random failure of user_limits.test mysqltest disconnect/connect-combo could be so quick that connect would hit the server before it had processed the disconnect. Since that resulted in one more concurrent connection than we meant to have, global or per-user max-user-connections could be exceeded. This could lead to "random" failures in tests that set those limits.
[22 Jul 8:58]
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/50164 2731 Tatiana A. Nurnberg 2008-07-21 [merge] Bug#23921: random failure of user_limits.test mysqltest disconnect/connect-combo could be so quick that connect would hit the server before it had processed the disconnect. Since that resulted in one more concurrent connection than we meant to have, global or per-user max-user-connections could be exceeded. This could lead to "random" failures in tests that set those limits.
[22 Jul 20:40]
Bugs System
Pushed into 5.1.26-rc
[24 Jul 15:28]
Georgi Kodinov
Still failing in 6.0-bugteam (prepared statements tests on 'sles10-ia64-a'. Disabling the test again
[28 Jul 16:06]
Bugs System
Pushed into 6.0.7-alpha (revid:alik@mysql.com-20080725172155-fnc73o50e4tgl23k) (pib:2)
[28 Jul 16:44]
Bugs System
Pushed into 6.0.7-alpha (revid:alik@mysql.com-20080725172155-fnc73o50e4tgl23k) (version source revid:alik@mysql.com-20080725172155-fnc73o50e4tgl23k) (pib:3)
[28 Jul 18:44]
Bugs System
Pushed into 5.1.28 (revid:davi.arnaut@sun.com-20080722182431-0i2f1yc4uocime9q) (version source revid:davi.arnaut@sun.com-20080722182431-0i2f1yc4uocime9q) (pib:3)
[18 Aug 19:16]
Paul DuBois
Noted in 5.1.26, 6.0.7 changelog. mysqltest was changed to be more robust in the case of a race condition that can occur for rapid disconnect/connect sequences with the server. The account used by mysqltest could reach its allowed simultaneous-sessions user limit if the connect attempt occurred before the server had fully processed the preceding disconnect. mysqltest now checks specificaly for a user-limits error when it connects; if that error occurs, it delays briefly before retrying.
[13 Sep 23:20]
Bugs System
Pushed into 6.0.7-alpha (revid:azundris@mysql.com-20080721102344-esynwn5hc5rv7dpx) (version source revid:hakan@mysql.com-20080725175322-8wgujj5xuzrjz3ke) (pib:3)
