InnoDB redo log resizing may crash if log tracking is enabled: Failing assertion: node->n_pending == 0 in fil0fil.cc line 899
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Invalid
|
Undecided
|
Unassigned | ||
5.6 |
Fix Released
|
Medium
|
Laurynas Biveinis |
Bug Description
With --innodb-
2013-07-22 11:45:38 21027 [Note] InnoDB: starting tracking changed pages from LSN 1625987
2013-07-22 11:45:38 21027 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*64 pages, LSN=1625987
2013-07-22 11:45:38 21027 [Warning] InnoDB: Starting to delete and rewrite log files.
2013-07-22 11:45:38 21027 [Note] InnoDB: Setting log file ./ib_logfile101 size to 1 MB
2013-07-22 11:45:38 21027 [Note] InnoDB: Setting log file ./ib_logfile1 size to 1 MB
2013-07-22 11:45:38 7f09b82817e0 InnoDB: Assertion failure in thread 139679721068512 in file fil0fil.cc line 899
InnoDB: Failing assertion: node->n_pending == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
11:45:38 UTC - mysqld got signal 6 ;
It occurs quite frequently in XB Jenkins after updating PS version used by the test suite from PS 5.6.10 to PS 5.6.11 (i.e. the one where page tracking is available: http://
It doesn't seem to occur with page tracking disabled, i.e. all xb_incremental_
I'm going to implement a workaround in XB tests for now so that the server doesn't have to resize the log files on startup, so this is not high priority.
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 234 lines (+109/-11)7 files modifiedmysql-test/suite/innodb/r/percona_changed_page_bmp_log_resize.result (+18/-0)
mysql-test/suite/innodb/t/percona_changed_page_bmp_log_resize-master.opt (+1/-0)
mysql-test/suite/innodb/t/percona_changed_page_bmp_log_resize.test (+64/-0)
storage/innobase/fil/fil0fil.cc (+6/-0)
storage/innobase/include/srv0srv.h (+6/-3)
storage/innobase/log/log0log.cc (+3/-5)
storage/innobase/srv/srv0srv.cc (+11/-3)
tags: | added: bitmap |
tags: | added: 56qual |
summary: |
- InnoDB: Failing assertion: node->n_pending == 0 in fil0fil.cc line 899 + InnoDB redo log resizing may crash if log tracking is enabled: Failing + assertion: node->n_pending == 0 in fil0fil.cc line 899 |
tags: | added: xtradb |
Indeed, log tracking initialization happens before the log file resizing.