[MDEV-6376]  InnoDB: Assertion failure in thread 139995225970432 in file buf0mtflu.cc line 570 Created: 2014-06-23  Updated: 2014-06-28  Resolved: 2014-06-28

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.15-FusionIO, 10.1.0
Fix Version/s: 10.0.15-FusionIO, 10.1.0

Type: Bug Priority: Major
Reporter: Jan Lindström (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: fusion-io, innodb


 Description   

InnoDB: Assertion failure in thread 139995225970432 in file buf0mtflu.cc line 570 InnoDB: Failing assertion: ib_wqueue_is_empty(mtflush_ctx->wq)

Analysis: Real timing bug, we should take the mutex before we try to send those shutdown messages, that would make sure that threads doing a unfinished flush (they have acquired this mutex) have time to do their work before we add shutdown messages to work queue. Currently, we just add those shutdown messages to work queue and code assumes that at flush, there is constant number of items to be processed and thus leading to assertion.

 Comments   
Comment by Jan Lindström (Inactive) [ 2014-06-26 ]

10.0:

revno: 3988
committer: Jan Lindström <jplindst@mariadb.org>
branch nick: 10.0-FusionIO-release
timestamp: Thu 2014-06-26 07:50:48 +0300
message:
MDEV-6361: innodb_compression_algorithm configuration variable can
be set to unsupported value.

MDEV-6350: Excessive unnecessary memory allocation at InnoDB/XtraDB
startup if LZO is installed.

MDEV-6376: InnoDB: Assertion failure in thread 139995225970432
in file buf0mtflu.cc line 570.

Comment by Jan Lindström (Inactive) [ 2014-06-28 ]

10.1:

commit b35c5912b651496ad5797bf85eaef3a431235e68
Author: Jan Lindström <jan.lindstrom@skysql.com>
Date: Sat Jun 28 13:53:18 2014 +0300

MDEV-6376: InnoDB: Assertion failure in thread 139995225970432
in file buf0mtflu.cc line 570.

Analysis: Real timing bug, we should take the mutex before we
try to send those shutdown messages, that would make sure
that threads doing a unfinished flush (they have acquired
this mutex) have time to do their work before we add shutdown
messages to work queue. Currently, we just add those shutdown
messages to work queue and code assumes that at flush, there
is constant number of items to be processed and thus
leading to assertion.

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