| Bug #44735 | The mysql cluster data node crash when dropping two big table | ||
|---|---|---|---|
| Submitted: | 8 May 2009 3:50 | Modified: | 17 Oct 2009 12:39 |
| Reporter: | Steven Fan | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Cluster: Disk Data | Severity: | S3 (Non-critical) |
| Version: | mysql-5.1-telco-6.3 | OS: | Linux (Linux acm-dev10-n1-int 2.6.15-1.2054_FC5smp #1 SMP Tue Mar 14 16:05:46 EST 2006 i686 i686 i386 GNU/L) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | 5.1.30-ndb-6.3.20-innodb, crash cluster | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[8 May 2009 3:52]
Steven Fan
[12 May 2009 2:31]
Steven Fan
the failing data nodes error and trace log files
Attachment: ndb_2_out.zip (application/x-zip-compressed, text), 10.74 KiB.
[12 May 2009 2:32]
Steven Fan
the failing data nodes error and trace log files
Attachment: ndb_2_error.log (application/octet-stream, text), 2.02 KiB.
[12 May 2009 2:34]
Steven Fan
the failing data nodes error and trace log files
Attachment: mysqllog.zip (application/x-zip-compressed, text), 48.51 KiB.
