| SitePoint Sponsor |
|
|
User Tag List
Results 1 to 3 of 3
Thread: Mis-configuring InnoDB
-
Mar 30, 2005, 18:19 #1SitePoint Wizard
- Join Date
- Jul 2003
- Location
- Corner seat
- Posts
- 1,069
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
Mis-configuring InnoDB
I've been having problems with my database, and it appears that one of causes is mis-configuration of InnoDB(MySQL).
q. Can mis-configuring InnoDB while there is a heavy load cause the database to lock up?
-
Mar 31, 2005, 08:22 #2SitePoint Zealot
- Join Date
- Mar 2005
- Location
- Houston, TX
- Posts
- 118
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
In what way is it mis-configured?
When you say MySQL locks up do you mean it is not accepting connections or processing queries? Or did it actually crash?
What OS and MySQL version?
-
Mar 31, 2005, 16:03 #3SitePoint Wizard
- Join Date
- Jul 2003
- Location
- Corner seat
- Posts
- 1,069
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
Currently my.ini has no variable defined for InnoDB; that's what I mean by mis-configured.
MySQL gets locked (partially?) and it creates number of errors: error log file shows "Lock" error messages. And, yes, the entire MySQL gets locked up at some point.
RHE, MySQL 3.23, Plesk7, Apache2.
Bookmarks