Bug #20676 | Sporadic failure of test case 'events_stress' | ||
---|---|---|---|
Submitted: | 24 Jun 2006 17:09 | ||
Reporter: | Kristian Nielsen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S2 (Serious) |
Version: | 5.1.12 | OS: | Linux (Linux) |
Assigned to: | Kristian Nielsen | CPU Architecture: | Any |
[24 Jun 2006 17:09]
Kristian Nielsen
[26 Jun 2006 12:13]
Kristian Nielsen
Hm, I think I know what the problem is here. The test case seems to create 250 simultaneous events that all do INSERT INTO events_test.fill_it Nothing wrong with that ... except that in mysys/thr_lock.c we have this: #define MAX_LOCKS 100 which cases it to put those warnings into the logfile when there are more than 100 waiters for a table, as there may easily be with 250 concurrent events. So should be simple to solve, pick one of these two options: 1. Reduce the number of events to 5*20 = 100 in the test case. 2. Increate the constant in thr_lock.c to 250.
[26 Jun 2006 13:52]
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/8245
[26 Jun 2006 17:10]
Kristian Nielsen
After discussion with Andrew, I modified the test to use different tables for different events classes. This avoids the only-100-waiters limitation. Pushed to 5.1.12. This is just a test suite failure, no user-visible bug. No documentation nedded.