| Bug #26783 | replication status unknown after cluster or mysqld failure | ||
|---|---|---|---|
| Submitted: | 2 Mar 2007 4:28 | Modified: | 11 Jun 2007 21:25 |
| Reporter: | Tomas Ulin | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Replication | Severity: | S4 (Feature request) |
| Version: | 5.1 | OS: | Any |
| Assigned to: | Tomas Ulin | CPU Architecture: | Any |
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
[3 Apr 2007 16:49]
Jonathan Miller
[3 Apr 2007 16:49]
Jonathan Miller
reject
Attachment: rpl_ndb_stm_innodb.reject (application/octet-stream, text), 7.30 KiB.
[3 Apr 2007 16:59]
Jonathan Miller
slave option file
Attachment: rpl_ndb_stm_innodb-slave.opt (application/octet-stream, text), 36 bytes.
[3 Apr 2007 16:59]
Jonathan Miller
master option file
Attachment: rpl_ndb_stm_innodb-master.opt (application/octet-stream, text), 41 bytes.
[3 Apr 2007 18:14]
Jonathan Miller
Updated test
Attachment: rpl_ndb_stm_innodb.test (application/octet-stream, text), 5.37 KiB.
[3 Apr 2007 18:14]
Jonathan Miller
Updated Reject
Attachment: rpl_ndb_stm_innodb.reject (application/octet-stream, text), 10.71 KiB.
