MySQL slave 延遲 外鍵檢查和自增加鎖

一、現象

延遲大，大事物。

• 表結構

• 無IO

• SQL THREAD占用CPU 100%

二、pscak 采樣

采樣30個點

• 外鍵檢查 占70%

• 自增鎖獲取 占30%

三、自增鎖獲取邏輯

邏輯如下其實也是innodb_autoinc_lock_mode參數的作用

switch (lock_mode) {
case AUTOINC_NO_LOCKING://innodb_autoinc_lock_mode=2
/* Acquire only the AUTOINC mutex. */
dict_table_autoinc_lock(m_prebuilt->table);
break;

case AUTOINC_NEW_STYLE_LOCKING: // innodb_autoinc_lock_mode=1 注意這里沒有break 巧妙的完成了邏輯
/* For simple (single/multi) row INSERTs, we fallback to the
old style only if another transaction has already acquired
the AUTOINC lock on behalf of a LOAD FILE or INSERT … SELECT
etc. type of statement. */
if (thd_sql_command(m_user_thd) == SQLCOM_INSERT
|| thd_sql_command(m_user_thd) == SQLCOM_REPLACE) {

dict_table_t* ib_table = m_prebuilt->table;

/* Acquire the AUTOINC mutex. */
dict_table_autoinc_lock(ib_table);

/* We need to check that another transaction isn’t
already holding the AUTOINC lock on the table. */
if (ib_table->n_waiting_or_granted_auto_inc_locks) {
/* Release the mutex to avoid deadlocks. */
dict_table_autoinc_unlock(ib_table);
} else {
break;
}
}
/* Fall through to old style locking. */

case AUTOINC_OLD_STYLE_LOCKING://innodb_autoinc_lock_mode=0 觸發
DBUG_EXECUTE_IF(“die_if_autoinc_old_lock_style_used”,
ut_ad(0););
error = row_lock_table_autoinc_for_mysql(m_prebuilt); //這個函數上表上的自增鎖

if (error == DB_SUCCESS) {

/* Acquire the AUTOINC mutex. */
dict_table_autoinc_lock(m_prebuilt->table);
}
break;

default:
ut_error;
}