Bug #59622 Data loss after crash at point crash_commit_after_prepare for binlog crash-safe
| Submitted: | 19 Jan 2011 22:29 | Modified: | 10 Feb 2011 8:03 |
|---|---|---|---|
| Reporter: | Serge Kozlov | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 5.5, trunk | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | crash, crash_commit_after_prepare, innodb, nuts, replication | ||
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
[25 Jan 2011 19:16]
Serge Kozlov
[28 Jan 2011 9:54]
Daogang Qu
The problem can be reproduced the attached test file.
Attachment: binlog_bug59622.test (application/octet-stream, text), 151.51 KiB.
[3 Feb 2011 12:10]
Marko Mäkelä
Reduced test case (fails some of the time)
Attachment: innodb_bug59622.test (application/octet-stream, text), 3.01 KiB.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.