腳本之家服務器常用軟件

快捷導航

區(qū)別于Oracle的MySQL?insert會阻塞update

更新時間：2023年03月29日 08:58:46 作者：GreatSQL

這篇文章主要介紹了區(qū)別于Oracle的MySQL?insert會阻塞update的問題解決，有需要的朋友可以借鑒參考下，希望能夠有所幫助，祝大家多多進步，早日升職加薪

正文

GreatSQL社區(qū)原創(chuàng)內容未經授權不得隨意使用，轉載請聯系小編并注明來源。
GreatSQL是MySQL的國產分支版本，使用上與MySQL一致。
作者：王慶勛
文章來源：GreatSQL社區(qū)原創(chuàng)

某銀行客戶在從Oracle遷移到MySQL的開發(fā)中，MySQL在READ-COMMITTED隔離級別下，出現了insert阻塞update的情況，但同樣的情況下，Oracle的insert則不會阻塞update。本文通過復現該問題，分析MySQL的鎖信息，確認是MySQL與Oracle在并發(fā)事務處理上的差異，在進行數據庫遷移改造的程序開發(fā)應予以關注。

1.問題復現

1.1.環(huán)境準備

MySQL版本的8.0.26，隔離級別是READ-COMMITTED ，測試表t的字段a為主鍵。

mysql&gt; select version();
+-----------+
| version() |
+-----------+
| 8.0.26    |
+-----------+
1 row in set (0.02 sec)
mysql&gt; show variables like 'transaction_isolation';
+-----------------------+----------------+
| Variable_name         | Value          |
+-----------------------+----------------+
| transaction_isolation | READ-COMMITTED |
+-----------------------+----------------+
1 row in set (0.00 sec)
mysql&gt; desc t;
+-------+------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------+------+------+-----+---------+-------+
| a     | int  | NO   | PRI | NULL    |       |
| b     | int  | YES  |     | NULL    |       |
+-------+------+------+-----+---------+-------+
2 rows in set (0.01 sec)
mysql&gt; select * from t;
+---+------+
| a | b    |
+---+------+
| 7 |    7 |
+---+------+
1 row in set (0.00 sec)

1.2. insert阻塞update的操作步驟

insert語句未提交時，update同樣主鍵的數據會被阻塞。

session1	session2
插入一條數據(a=8)后未提交。 mysql> begin; Query OK, 0 rows affected (0.00 sec) mysql> insert into t values(8,8); Query OK, 1 row affected (0.01 sec)
	更改數據，條件是a=8,將會被阻塞 mysql> update t set b=0 where a=8; <<掛起，等待innodb_lock_wait_timeout超時

2.分析原因

2.1.檢查事務鎖信息

mysql&gt; select * from information_schema.innodb_trx\G
*************************** 1. row ***************************
                    trx_id: 3795
                 trx_state: LOCK WAIT
               trx_started: 2022-10-11 16:03:38
     trx_requested_lock_id: 139727275779216:52:4:3:139724882995456
          trx_wait_started: 2022-10-11 16:03:38
                trx_weight: 2
       trx_mysql_thread_id: 9346
                 trx_query: update t set b=0 where a=8
       trx_operation_state: starting index read
         trx_tables_in_use: 1
         trx_tables_locked: 1
          trx_lock_structs: 2
     trx_lock_memory_bytes: 1128
           trx_rows_locked: 1
         trx_rows_modified: 0
   trx_concurrency_tickets: 0
       trx_isolation_level: READ COMMITTED
         trx_unique_checks: 1
    trx_foreign_key_checks: 1
trx_last_foreign_key_error: NULL
 trx_adaptive_hash_latched: 0
 trx_adaptive_hash_timeout: 0
          trx_is_read_only: 0
trx_autocommit_non_locking: 0
       trx_schedule_weight: 1
*************************** 2. row ***************************
                    trx_id: 3790
                 trx_state: RUNNING
               trx_started: 2022-10-11 16:03:29
     trx_requested_lock_id: NULL
          trx_wait_started: NULL
                trx_weight: 3
       trx_mysql_thread_id: 9320
                 trx_query: NULL
       trx_operation_state: NULL
         trx_tables_in_use: 0
         trx_tables_locked: 1
          trx_lock_structs: 2
     trx_lock_memory_bytes: 1128
           trx_rows_locked: 1
         trx_rows_modified: 1
   trx_concurrency_tickets: 0
       trx_isolation_level: READ COMMITTED
         trx_unique_checks: 1
    trx_foreign_key_checks: 1
trx_last_foreign_key_error: NULL
 trx_adaptive_hash_latched: 0
 trx_adaptive_hash_timeout: 0
          trx_is_read_only: 0
trx_autocommit_non_locking: 0
       trx_schedule_weight: NULL
2 rows in set (0.00 sec)
說明：通過InnoDB的事務表innodb_trx查詢到thread_id=9346的事務3795正在等待鎖（trx_state: LOCK WAIT）,
thread_id=9320的事務3790正在執(zhí)行（trx_state: RUNNING）。
mysql&gt; select * from performance_schema.data_locks\G
*************************** 1. row ***************************
               ENGINE: INNODB
       ENGINE_LOCK_ID: 139727275779216:1113:139724882998560
ENGINE_TRANSACTION_ID: 3795
            THREAD_ID: 9441
             EVENT_ID: 5000
        OBJECT_SCHEMA: testdb
          OBJECT_NAME: t
       PARTITION_NAME: NULL
    SUBPARTITION_NAME: NULL
           INDEX_NAME: NULL
OBJECT_INSTANCE_BEGIN: 139724882998560
            LOCK_TYPE: TABLE
            LOCK_MODE: IX
          LOCK_STATUS: GRANTED
            LOCK_DATA: NULL
*************************** 2. row ***************************
               ENGINE: INNODB
       ENGINE_LOCK_ID: 139727275779216:52:4:3:139724882995456
ENGINE_TRANSACTION_ID: 3795
            THREAD_ID: 9441
             EVENT_ID: 5012
        OBJECT_SCHEMA: testdb
          OBJECT_NAME: t
       PARTITION_NAME: NULL
    SUBPARTITION_NAME: NULL
           INDEX_NAME: PRIMARY
OBJECT_INSTANCE_BEGIN: 139724882995456
            LOCK_TYPE: RECORD
            LOCK_MODE: X,REC_NOT_GAP
          LOCK_STATUS: WAITING
            LOCK_DATA: 8
*************************** 3. row ***************************
               ENGINE: INNODB
       ENGINE_LOCK_ID: 139727275781640:1113:139724883017072
ENGINE_TRANSACTION_ID: 3790
            THREAD_ID: 9415
             EVENT_ID: 15467
        OBJECT_SCHEMA: testdb
          OBJECT_NAME: t
       PARTITION_NAME: NULL
    SUBPARTITION_NAME: NULL
           INDEX_NAME: NULL
OBJECT_INSTANCE_BEGIN: 139724883017072
            LOCK_TYPE: TABLE
            LOCK_MODE: IX
          LOCK_STATUS: GRANTED
            LOCK_DATA: NULL
*************************** 4. row ***************************
               ENGINE: INNODB
       ENGINE_LOCK_ID: 139727275781640:52:4:3:139724883013968
ENGINE_TRANSACTION_ID: 3790
            THREAD_ID: 9441
             EVENT_ID: 5007
        OBJECT_SCHEMA: testdb
          OBJECT_NAME: t
       PARTITION_NAME: NULL
    SUBPARTITION_NAME: NULL
           INDEX_NAME: PRIMARY
OBJECT_INSTANCE_BEGIN: 139724883013968
            LOCK_TYPE: RECORD
            LOCK_MODE: X,REC_NOT_GAP
          LOCK_STATUS: GRANTED
            LOCK_DATA: 8
4 rows in set (0.00 sec)
說明：事務3795正在等待LOCK_TYPE: RECORD，LOCK_MODE:X,REC_NOT_GAP，等待的主鍵值為8；
事務3790已獲取主鍵值為8的LOCK_TYPE: RECORD，LOCK_MODE:X,REC_NOT_GAP鎖。
mysql&gt; select * from sys.innodb_lock_waits\G
*************************** 1. row ***************************
                wait_started: 2022-10-11 16:03:38
                    wait_age: 00:02:50
               wait_age_secs: 170
                locked_table: `testdb`.`t`
         locked_table_schema: testdb
           locked_table_name: t
      locked_table_partition: NULL
   locked_table_subpartition: NULL
                locked_index: PRIMARY
                 locked_type: RECORD
              waiting_trx_id: 3795
         waiting_trx_started: 2022-10-11 16:03:38
             waiting_trx_age: 00:02:50
     waiting_trx_rows_locked: 1
   waiting_trx_rows_modified: 0
                 waiting_pid: 9346
               waiting_query: update t set b=0 where a=8
             waiting_lock_id: 139727275779216:52:4:3:139724882995456
           waiting_lock_mode: X,REC_NOT_GAP
             blocking_trx_id: 3790
                blocking_pid: 9320
              blocking_query: NULL
            blocking_lock_id: 139727275781640:52:4:3:139724883013968
          blocking_lock_mode: X,REC_NOT_GAP
        blocking_trx_started: 2022-10-11 16:03:29
            blocking_trx_age: 00:02:59
    blocking_trx_rows_locked: 1
  blocking_trx_rows_modified: 1
     sql_kill_blocking_query: KILL QUERY 9320
sql_kill_blocking_connection: KILL 9320
1 row in set (0.01 sec)
說明：事務3795等待testdb.t上的rec_not_gap獨占鎖，事務3790持有該獨占鎖。
mysql&gt; select distinct,* from sys.processlist where conn_id in (select trx_mysql_thread_id from information_schema.innodb_trx)\G
*************************** 1. row ***************************
                thd_id: 9441
               conn_id: 9346
                  user: admin@172.17.128.73
                    db: testdb
               command: Query
                 state: updating
                  time: 141
     current_statement: update t set b=0 where a=8
     statement_latency: 2.37 min
              progress: NULL
          lock_latency: 431.00 us
         rows_examined: 0
             rows_sent: 0
         rows_affected: 0
            tmp_tables: 0
       tmp_disk_tables: 0
             full_scan: NO
        last_statement: NULL
last_statement_latency: NULL
        current_memory: 140.15 KiB
             last_wait: wait/io/table/sql/handler
     last_wait_latency: Still Waiting
                source: handler.cc:3250
           trx_latency: 13.30 min
             trx_state: ACTIVE
        trx_autocommit: NO
                   pid: 9632
          program_name: mysql
*************************** 2. row ***************************
                thd_id: 9415
               conn_id: 9320
                  user: admin@172.17.128.73
                    db: testdb
               command: Sleep
                 state: NULL
                  time: 801
     current_statement: NULL
     statement_latency: NULL
              progress: NULL
          lock_latency: 288.00 us
         rows_examined: 0
             rows_sent: 0
         rows_affected: 1
            tmp_tables: 0
       tmp_disk_tables: 0
             full_scan: NO
        last_statement: insert into t values(8,8)
last_statement_latency: 765.23 us
        current_memory: 218.19 KiB
             last_wait: wait/io/socket/sql/client_connection
     last_wait_latency: Still Waiting
                source: viosocket.cc:146
           trx_latency: 13.52 min
             trx_state: ACTIVE
        trx_autocommit: NO
                   pid: 9600
          program_name: mysql
說明：被阻塞事務執(zhí)行的sql語句update t set b=0 where a=8，
阻塞事務執(zhí)行的sql語句是insert into t values(8,8)。

說明：

MySQL的隔離級別是通過索引上的鎖實現并發(fā)事務控制的。在READ-COMMITTED隔離級別下，session1在執(zhí)行insert語句時，在主鍵索引上獲取了a=8的行記錄獨占鎖，以禁止插入相同主鍵的數據；session2如果同時插入相同的主鍵數據被阻塞，容易理解（Oracle也同樣阻塞）。出于同樣的原因session2執(zhí)行update時，由于無法獲取a=8的行記錄獨占鎖，同樣也會被阻塞。

2.2.驗證MySQL事務未提交時已寫入數據文件

驗證事務未提交時，insert語句已將數據寫入數據文件，索引數據也已生成。

測試表test1
mysql&gt; CREATE TABLE `test1` (
    -&gt;   `id` int NOT NULL AUTO_INCREMENT,
    -&gt;   `k` int NOT NULL DEFAULT '0',
    -&gt;   `c` char(120) NOT NULL DEFAULT '',
    -&gt;   `pad` char(60) NOT NULL DEFAULT '',
    -&gt;   PRIMARY KEY (`id`),
    -&gt;   KEY `k_1` (`k`)
    -&gt; ) ;
Query OK, 0 rows affected (0.07 sec)
開啟一個事務，插入10萬條數據。
mysql&gt; begin;
Query OK, 0 rows affected (0.00 sec)
mysql&gt; insert into test1 select * from sbtest1;
Query OK, 100000 rows affected (1.44 sec)
Records: 100000  Duplicates: 0  Warnings: 0
檢查表的data_length和index_length
mysql&gt; show table status where name like 'test1'\G
*************************** 1. row ***************************
           Name: test1
         Engine: InnoDB
        Version: 10
     Row_format: Dynamic
           Rows: 98712
 Avg_row_length: 228
    Data_length: 22593536
Max_data_length: 0
   Index_length: 2637824
      Data_free: 4194304
 Auto_increment: 100001
    Create_time: 2022-10-11 22:14:50
    Update_time: NULL
     Check_time: NULL
      Collation: utf8mb4_0900_ai_ci
       Checksum: NULL
 Create_options: 
        Comment: 
1 rows in set (0.01 sec)
回滾insert操作
mysql&gt; rollback;
Query OK, 0 rows affected (1.35 sec)
更新統計信息
mysql&gt; analyze table test1;
再次檢查表的data_length和index_length
mysql&gt; show table status where name like 'test1'\G 
*************************** 1. row ***************************
           Name: test1
         Engine: InnoDB
        Version: 10
     Row_format: Dynamic
           Rows: 0
 Avg_row_length: 0
    Data_length: 16384
Max_data_length: 0
   Index_length: 16384
      Data_free: 29360128
 Auto_increment: 100001
    Create_time: 2022-10-11 22:22:36
    Update_time: NULL
     Check_time: NULL
      Collation: utf8mb4_0900_ai_ci
       Checksum: NULL
 Create_options: 
        Comment: 
1 row in set (0.00 sec)
檢查數據文件的大小
[root@host73 testdb]# ll *test1.ibd
-rw-r----- 1 greatdb greatdb 30408704 Oct 11 15:12 sbtest1.ibd
-rw-r----- 1 greatdb greatdb 33554432 Oct 11 22:24 test1.ibd

說明：

MySQL在執(zhí)行insert 語句進行數據插入，未提交時，數據也已寫入表的聚集索引，輔助索引也已生成。MySQL可以使用未提交數據的索引，通過鎖機制實現事務的并發(fā)控制。

3.Oracle中insert沒有阻塞update

在Oracle中，創(chuàng)建同樣的測試表t，執(zhí)行同樣的insert和update，但insert不會阻塞update。

CREATE TABLE t (
  a int NOT NULL PRIMARY KEY ,
  b int DEFAULT NULL
);
insert into t values(7,7);
commit;

執(zhí)行相同的insert和update語句。

session1	session2
SQL> insert into t values(8,8);
1 row created.	SQL> update t set b=0 where a=8;0 rows updated.
---

Enjoy GreatSQL :)

關于 GreatSQL

GreatSQL是由萬里數據庫維護的MySQL分支，專注于提升MGR可靠性及性能，支持InnoDB并行查詢特性，是適用于金融級應用的MySQL分支版本。

相關鏈接：

以上就是區(qū)別于Oracle的MySQL insert會阻塞update的詳細內容，更多關于MySQL insert阻塞update的資料請關注腳本之家其它相關文章！

您可能感興趣的文章:

亚洲乱码中文字幕综合,中国熟女仑乱hd,亚洲精品乱拍国产一区二区三区,一本大道卡一卡二卡三乱码全集资源,又粗又黄又硬又爽的免费视频

區(qū)別于Oracle的MySQL?insert會阻塞update

目錄

正文

1.問題復現

1.1.環(huán)境準備

1.2. insert阻塞update的操作步驟

2.分析原因

2.1.檢查事務鎖信息

2.2.驗證MySQL事務未提交時已寫入數據文件

3.Oracle中insert沒有阻塞update

關于 GreatSQL

相關文章

最新評論

大家感興趣的內容

最近更新的內容

常用在線小工具