Bug #25820 | CPU pegged at 100% after optimizing table belonging to merge set | ||
---|---|---|---|
Submitted: | 24 Jan 2007 11:15 | Modified: | 12 Feb 2007 9:17 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
Version: | 5.0.36BK | OS: | Any (*) |
Assigned to: | CPU Architecture: | Any | |
Tags: | cpu, hang, merge, Optimize |
[24 Jan 2007 11:15]
Shane Bester
[24 Jan 2007 11:27]
MySQL Verification Team
stack trace of the thread which is stuck looping
Attachment: thread_stack_5.0.36_windows.txt (text/plain), 1.91 KiB.
[12 Feb 2007 9:17]
MySQL Verification Team
Just realized this is a duplicate of bug #25966 Sorry for any inconvenience caused. It's pegged at 100% cpu because there's continuous memory allocations going on. I hadn't noticed it immediately when filing this bug report (Was looking for another specific bug). Also, it's NOT merge specific, just was easier to reproduce with merge tables.