mariadb/storage/innobase/srv
Thirunarayanan Balathandayuthapani e706324205 MDEV-35863 innodb.doublewrite_debug test case fails to start the server
Problem:
=======
- There are two failures occurs for this test case:

(1) set global innodb_buf_flush_list_now=1 doesn't make sure that pages
are being flushed.

(2) InnoDB page cleaner thread aborts while writing the checkpoint information.
Problem is that When InnoDB startup aborts, InnoDB changes the shutdown
state to SRV_SHUTDOWN_EXIT_THREADS. By changing the shutdown state, InnoDB
doesn't advance the log_sys.lsn (avoids fil_names_clear()).
After InnoDB shutdown(innodb_shutdown()) is being initiated, shutdown state
again changed to SRV_SHUTDOWN_INITIATED. This leads the page cleaner thread
to fail with assertion ut_ad(srv_shutdown_state > SRV_SHUTDOWN_INITIATED)
in log_write_checkpoint_info()

Solution:
=========
(1)  In order to avoid (1) failure, InnoDB can make the
variable innodb_max_dirty_pages_pct_lwm, innodb_max_dirty_pages_pct to 0.
Also make sure that InnoDB doesn't have any dirty pages in buffer pool
by adding wait_condition.

(2) Avoid changing the srv_shutdown_state to SRV_SHUTDOWN_EXIT_THREADS
when the InnoDB startup aborts
2025-06-23 15:48:43 +05:30
..
srv0mon.cc MDEV-33613 InnoDB may still hang when temporarily running out of buffer pool 2024-03-22 14:17:39 +02:00
srv0srv.cc MDEV-36226 Stall and crash when page cleaner fails to generate free pages during Async flush 2025-03-31 19:09:23 +05:30
srv0start.cc MDEV-35863 innodb.doublewrite_debug test case fails to start the server 2025-06-23 15:48:43 +05:30