Innodb: 自動開啟列印show engine status到err日誌
一、問題描述
為什麼我的err日誌裡面有大量的show engine innodb status的記錄，我自己並沒有開啟innodb_status_output引數。
二、問題分析
通過檢視日誌，發現如下輸出：
2019-03-21T17:00:02.375231Z 1230497 [Warning] InnoDB: Difficult to find free blocks in the buffer pool (338 search iterations)! 0 failed attempts to flush a page! Consider increasing the buffer pool size. It is also possible
that in your Unix version fsync is very slow, or completely frozen inside the OS kernel. Then upgrading to a
newer version of your operating system may help. Look at the number of fsyncs in diagnostic info below.
Pending flushes (fsync) log: 0; buffer pool: 0. 1446962050 OS file reads, 545881917 OS file writes,
376257282 OS fsyncs. Starting InnoDB Monitor to print further diagnostics to the standard output.
日誌也寫得很清楚。應該是free block不夠了Innodb自動開啟了。但是我們需要原始碼驗證一下。
三、原始碼驗證
在原始碼的buf_LRU_handle_lack_of_free_blocks函式中我們看到如下：
if ((current_ms > started_ms + 2000)
&& (current_ms > last_printout_ms + 2000)
&& srv_buf_pool_old_size == srv_buf_pool_size) {
ib::warn() << "Difficult to find free blocks in the buffer pool"
" (" << n_iterations << " search iterations)! "
<< flush_failures << " failed attempts to"
" flush a page! Consider increasing the buffer pool"
" size. It is also possible that in your Unix version"
" fsync is very slow, or completely frozen inside"
" the OS kernel. Then upgrading to a newer version"
" of your operating system may help. Look at the"
" number of fsyncs in diagnostic info below."
" Pending flushes (fsync) log: "
<< fil_n_pending_log_flushes
<< "; buffer pool: "
<< fil_n_pending_tablespace_flushes
<< ". " << os_n_file_reads << " OS file reads, "
<< os_n_file_writes << " OS file writes, "
<< os_n_fsyncs
<< " OS fsyncs. Starting InnoDB Monitor to print"
" further diagnostics to the standard output.";
last_printout_ms = current_ms;
*mon_value_was = srv_print_innodb_monitor;
*started_monitor = true;
srv_print_innodb_monitor = true;
os_event_set(srv_monitor_event);
這裡不僅打印出了日誌同時設定了引數srv_print_innodb_monitor = true; 並且開始os_event_set(srv_monitor_event);開啟了monitor列印執行緒。那我們看看srv_print_innodb_monitor 對應什麼引數呢。如下：
static MYSQL_SYSVAR_BOOL(status_output, srv_print_innodb_monitor,
PLUGIN_VAR_OPCMDARG, "Enable InnoDB monitor output to the error log.", NULL, innodb_status_output_update, FALSE);
實際上就是innodb_status_output被自動開了。當然如果檢視呼叫可以在上層函式buf_LRU_get_free_block中檢視到呼叫，實際上就是在free list找不到空閒的block的時候會做輸出。buf_LRU_get_free_block還包含了一個塊的分配流程大約如下，可自行參考：
- If there is a block in the free list, take it .如果這裡找不到就會自動開啟innodb_status_output
- If no block was in the free list, search from the end of the LRU list and try to free a block there.
- No free block was found: try to flush the LRU list.
Linux公社的RSS地址 ：https://www.linuxidc.com/rssFeed.aspx
本文永久更新連結地址：https://www.linuxidc.com/Linux/2019-04/157971.htm