Bug #48946 | seemingly bogus error: Operating system error number 1450 in a file operation. | ||
---|---|---|---|
Submitted: | 20 Nov 2009 15:49 | Modified: | 27 Sep 2010 14:24 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB Plugin storage engine | Severity: | S3 (Non-critical) |
Version: | 5.1.41 | OS: | Windows (XP64) |
Assigned to: | CPU Architecture: | Any |
[20 Nov 2009 15:49]
Shane Bester
[20 Nov 2009 21:04]
MySQL Verification Team
potential build error here...need second opinion. the plugin .dll is built with a 10000000 byte stack reserve size for each thread. this means each innodb thread will transparently consume just under 10M of memory, and this will not show in task manager, or in the innodb status. the mysqld.exe itself has a stack reserve of 1M which is fine ( remember bug #20815 )
[26 Nov 2009 6:49]
Calvin Sun
Shane - you may try to build the plugin into the server (as a static library), to see whether you can reproduce the problem. Also, monitor the "Paged Pool" size of mysqld when the problem occurs. How about reduce the open-files-limit from 2000 to a much smaller number?
[27 Sep 2010 14:24]
MySQL Verification Team
haven't seen the error 1450 in many versions..