Bug #3424 | Creating full text Index on a table halts all other process. | ||
---|---|---|---|
Submitted: | 8 Apr 2004 19:22 | Modified: | 28 Apr 2004 13:44 |
Reporter: | Padmanabhan Krishnamoorthy | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 4.1.0-alpha | OS: | FreeBSD (FreeBSD 4.8-RELEASE-p13) |
Assigned to: | CPU Architecture: | Any |
[8 Apr 2004 19:22]
Padmanabhan Krishnamoorthy
[19 Apr 2004 18:51]
Padmanabhan Krishnamoorthy
The problem continues to exist and any help would be really apprecited.
[28 Apr 2004 13:44]
Alexander Keremidarski
Sorry, but the bug system is not the appropriate forum for asking support questions. Your problem is not the result of a bug. For a list of more appropriate places to ask for help using MySQL products, please visit http://www.mysql.com/support/ Thank you for your interest in MySQL. Additional info: Full Text engine is known to be high CPU bound, but acording to your top output this is not the case: CPU states: ... 78.4% idle It looks more like disk I/O problem which is OS and configuration problem, not MySQL one. Hint: Put datadir and tmpdir on dedicated (and separate) hard disks. Use vmstat, iostat