Bug #14966 | MySQL Cluster cannot complete system recovery | ||
---|---|---|---|
Submitted: | 16 Nov 2005 0:49 | Modified: | 10 Feb 2006 13:14 |
Reporter: | Kenji Hirohama | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 5.0.15 | OS: | Miracle Linux V3.0 |
Assigned to: | CPU Architecture: | Any |
[16 Nov 2005 0:49]
Kenji Hirohama
[16 Nov 2005 1:19]
Jonathan Miller
Can you attach the trace log from the failing data node?
[21 Nov 2005 5:18]
Kenji Hirohama
FYI, I tried smaller-data-size with the same table schema, then system recovery worked well. The output of "all dump 1000" is; 2005-11-21 11:57:15 [MgmSrvr] INFO -- Node 2: Data usage is 17%(28131 32K pages of total 160000) 2005-11-21 11:57:15 [MgmSrvr] INFO -- Node 2: Index usage is 2%(3929 8K pages of total 192032) It means; 900192k + 31432k = 931,624k = 930MB MySQL Cluster is using 930MB memory for data store.
[10 Jan 2006 13:14]
Hartmut Holzgraefe
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL. Additional info: Hi Kenji, you can upload large files to ftp://ftp.mysql.com/pub/mysql/upload. Please use filenames that include "bug14996". If the upload exceeds 10GB then please let us know so before uploading
[11 Feb 2006 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".