| Bug #25286 | NDB data node crashed in DBLQH, Line 2483 | ||
|---|---|---|---|
| Submitted: | 26 Dec 2006 21:10 | Modified: | 14 Mar 2007 10:08 |
| Reporter: | Anatoly Pidruchny (Candidate Quality Contributor) | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.1.14 | OS: | Linux (Linux x86_64) |
| Assigned to: | Jonas Oreland | CPU Architecture: | Any |
| Tags: | qc | ||
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
[26 Dec 2006 21:17]
Anatoly Pidruchny
[26 Dec 2006 21:17]
Anatoly Pidruchny
Trace log of the crashed data node
Attachment: ndb_3_trace.log.1.gz (application/x-gzip, text), 64.58 KiB.
[26 Dec 2006 21:18]
Anatoly Pidruchny
Out log of the crashed data node
Attachment: ndb_3_out.log.gz (application/x-gzip, text), 20.89 KiB.
[26 Dec 2006 21:18]
Anatoly Pidruchny
Cluster log file
Attachment: ndb_1_cluster.log.gz (application/x-gzip, text), 67.47 KiB.
