[MDEV-12127] InnoDB: Assertion failure loop_count < 5 in file log0log.cc Created: 2017-02-24  Updated: 2017-02-28  Resolved: 2017-02-28

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0, 10.1
Fix Version/s: 10.0.30, 10.1.22

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: upstream


 Description   

https://internal.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/9920/steps/test/logs/stdio

2017-02-24 17:08:59 132b6700  InnoDB: Assertion failure in thread 321611520 in file log0log.cc line 1576
InnoDB: Failing assertion: loop_count < 5

Found my old upstream bug report, it's still open:
https://bugs.mysql.com/bug.php?id=58536

Maybe it makes sense to do something about it, at least to increase the count as suggested in the comments.



 Comments   
Comment by Marko Mäkelä [ 2017-02-28 ]

10.0 fc673a2c121 MDEV-12127 InnoDB: Assertion failure loop_count < 5 in file log0log.cc

Comment by Jan Lindström (Inactive) [ 2017-02-28 ]

ok to push, in my opinion these kinds of trivial changes do not require review.

Comment by Marko Mäkelä [ 2017-02-28 ]

MariaDB Server 10.2.2 imported a change of the limit to 128 from MySQL 5.7.9. My patch raises the limit to 100 in 10.0 and 10.1.

The MySQL bug assignee changed the MySQL 5.7 code with a message that gives the wrong impression that no functional changes are present: "WL#6044 - Code cleanup."

Generated at Thu Feb 08 07:55:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.