Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5.5, 10.2(EOL), 10.3(EOL)
Description
Observed on buildbot, 64-bit Windows, debug:
CURRENT_TEST: innodb.group_commit_crash_no_optimize_thread
|
…
|
2017-09-17 10:58:59 4604 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1682230
|
Assertion failed: recv_sys->mlog_checkpoint_lsn <= recv_sys->recovered_lsn, file D:\winx64-debug\build\src\storage\innobase\log\log0recv.cc, line 2374
|
…
|
----------SERVER LOG END-------------
|
mysqltest failed but provided no output
|
The result from queries just before the failure was:
|
< snip >
|
a b c d 2
|
a b c d 3
|
a b c d 4
|
a b c d 5
|
a b c d 6
|
a b c d 7
|
a b c d 8
|
a b c d 9
|
a b c d 10
|
SHOW BINLOG EVENTS LIMIT 4,1;
|
Log_name Pos Event_type Server_id End_log_pos Info
|
master-bin.000001 # Query 1 # use `test`; insert into t1 select * from t2
|
delete from t1;
|
SET binlog_format= mixed;
|
RESET MASTER;
|
START TRANSACTION;
|
insert into t1 select * from t2;
|
call setcrash(2);
|
COMMIT;
|
Got one of the listed errors
|
This logic will be removed altogether when MDEV-14425 introduces a separate file for log checkpoints and file names.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
MDEV-14425 Change the InnoDB redo log format to reduce write amplification
-
- Closed
-
-
-
- Closed
-