[MDEV-11710] thd_destructor_proxy() hangs on shutdown after aborted startup Created: 2017-01-03  Updated: 2017-01-28  Resolved: 2017-01-28

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2.3
Fix Version/s: 10.2.4

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: innodb

Issue Links:
Problem/Incident
causes MDEV-11689 Server shuts down in unclean fashion ... Closed
is caused by MDEV-5800 indexes on virtual (not materialized)... Closed

 Description   

When MariaDB Server is started with an invalid option that causes InnoDB startup to be aborted, the thd_destructor_proxy() thread (which was introduced in MDEV-5800) gets stuck, causing an error message and assertion failure:

Error in my_thread_global_end(): 1 threads didn't exit
 
 
 
mysqld: /home/marko/mariadb/server/sql/mysqld.cc:2154: void mysqld_exit(int): Assertion `global_status_var.global_memory_used == 0' failed.



 Comments   
Comment by Marko Mäkelä [ 2017-01-03 ]

To repeat, use

./mtr --mysqld=--innodb-flush-method=foo innodb.innodb

Note: Without the MDEV-11688 fix, an InnoDB assertion will fail.

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