Bug #29808 | Enabling "Preload Buffer Size" causes Server crashing after reboot | ||
---|---|---|---|
Submitted: | 15 Jul 2007 10:40 | Modified: | 29 Oct 2009 15:49 |
Reporter: | Nicolas Wallner | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 1.2.12, 1.2.16 | OS: | Windows |
Assigned to: | Johannes Taxacher | CPU Architecture: | Any |
Tags: | preload_buffer_size |
[15 Jul 2007 10:40]
Nicolas Wallner
[16 Jul 2007 5:16]
Valeriy Kravchuk
Thank you for a bug report. Verified just as described on Windows XP.
[27 Jan 2009 12:40]
Louis Breda van
Hello, Just for info this problem is still there with version 1.2.15 jan 27 2009 Can not be too hard to fix !? Louis
[25 Feb 2009 12:15]
Susanne Ebrecht
Verified as described. The problem is: when you enable preload_buffer_size then the following will be attached at my.ini: # Number of threads allowed inside the InnoDB kernel. The optimal value # depends highly on the application, hardware as well as the OS # scheduler properties. A too high value may lead to thread thrashing. innodb_thread_concurrency=8 #The size of the buffer that is allocated when preloading indexes preload_buffer_size=32k As you see there is the single word "indexes" in an extra line without #. Here the # is missing and that is confusing the server.
[30 Apr 2009 8:29]
Elvis Dominguez
+1 same thing appens on UBUNTU 9.04, MySQL Admin Tools version 1.2.12
[15 Oct 2009 8:56]
Susanne Ebrecht
It is necessary to test, if this behaviour still occurs in Workbench 5.2.
[29 Oct 2009 15:49]
Johannes Taxacher
Workbench 5.2 does not show this behaviour anymore.