InnoDB: Warning: a long semaphore wait 解决办法

在导入大量数据到MySQL时遇到InnoDB长信号量等待错误,通过调整Linux内核信号量设置解决了该问题。涉及的具体步骤包括修改sysctl.conf文件、重启MySQL等。

mysqldump导入大量数据,error log报这个错


今天查看数据库错误日志,发现有InnoDB: Warning: a long semaphore wait:  报错:

解决办法:

原来Linux内核信号量默认设置太小,造成大量等待, 
默认 
# cat /proc/sys/kernel/sem 
250     32000   32      128 
说明: 
第一列,表示每个信号集中的最大信号量数目。 
第二列,表示系统范围内的最大信号量总数目。 
第三列,表示每个信号发生时的最大系统操作数目。 
第四列,表示系统范围内的最大信号集总数目。


将第三列调大一点,参考网上的数据 
echo "kernel.sem=250 32000 100 128″>>/etc/sysctl.conf 
然后sysctl -p 
重启MySQL

错误不再出现,问题即可解决


具体详细的报错如下,详细的对比参考:

InnoDB: Warning: a long semaphore wait:                                                                                 

  813 --Thread 139957495039744 has waited at btr0cur.cc line 545 for 241.00 seconds the semaphore:
  814 X-lock (wait_ex) on RW-latch at 0x7f4a60043da8 created in file dict0dict.cc line 2341
  815 a writer (thread id 139957495039744) has reserved it in mode  wait exclusive
  816 number of readers 2, waiters flag 1, lock_word: fffffffffffffffe
  817 Last time read locked in file btr0cur.cc line 554

  818 Last time write locked in file /root/mysql-5.6.10/storage/innobase/btr/btr0cur.cc line 545
  819 InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
  820 InnoDB: Pending preads 109, pwrites 0
  821 
  822 =====================================
  823 2014-04-21 18:27:21 7f4899a00700 INNODB MONITOR OUTPUT
  824 =====================================
  825 Per second averages calculated from the last 57 seconds
  826 -----------------
  827 BACKGROUND THREAD
  828 -----------------
  829 srv_master_thread loops: 704 srv_active, 0 srv_shutdown, 184 srv_idle
cndb012.5405.zr.sh.gcimg.net.err [RO]                                                                       812,1           6%


[root@cndb012 mysql]# cat /proc/sys/kernel/sem                                                                     
250     32000   32      128
[root@cndb012 mysql]# vim cndb012.5405.zr.sh.gcimg.net.err


  805 2014-04-21 18:04:55 16100 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000124', position 61975299
  812 InnoDB: Warning: a long semaphore wait:
  813 --Thread 139957495039744 has waited at btr0cur.cc line 545 for 241.00 seconds the semaphore:
  814 X-lock (wait_ex) on RW-latch at 0x7f4a60043da8 created in file dict0dict.cc line 2341
  815 a writer (thread id 139957495039744) has reserved it in mode  wait exclusive
  816 number of readers 2, waiters flag 1, lock_word: fffffffffffffffe
  817 Last time read locked in file btr0cur.cc line 554
  818 Last time write locked in file /root/mysql-5.6.10/storage/innobase/btr/btr0cur.cc line 545
  819 InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
  820 InnoDB: Pending preads 109, pwrites 0
  821 
  822 =====================================
  823 2014-04-21 18:27:21 7f4899a00700 INNODB MONITOR OUTPUT
  824 =====================================
  825 Per second averages calculated from the last 57 seconds
  826 -----------------
  827 BACKGROUND THREAD
  828 -----------------
  829 srv_master_thread loops: 704 srv_active, 0 srv_shutdown, 184 srv_idle
  830 srv_master_thread log flush and writes: 887
  831 ----------
  832 SEMAPHORES
  833 ----------
  834 OS WAIT ARRAY INFO: reservation count 75098
  835 --Thread 139948735776512 has waited at row0sel.cc line 3048 for 0.00 seconds the semaphore:
  836 S-lock on RW-latch at 0x7f48aa6535c0 created in file buf0buf.cc line 994
  837 a writer (thread id 139957491046144) has reserved it in mode  exclusive
  838 number of readers 0, waiters flag 1, lock_word: 0
  839 Last time read locked in file not yet reserved line 0
  840 Last time write locked in file /root/mysql-5.6.10/storage/innobase/buf/buf0buf.cc line 3466
  841 --Thread 139949644658432 has waited at row0sel.cc line 4111 for 1.00 seconds the semaphore:
  842 S-lock on RW-latch at 0x7f49d1bd1ec0 created in file buf0buf.cc line 994
  843 a writer (thread id 139948734711552) has reserved it in mode  exclusive
  844 number of readers 0, waiters flag 1, lock_word: 0
  845 Last time read locked in file not yet reserved line 0
  846 Last time write locked in file /root/mysql-5.6.10/storage/innobase/buf/buf0buf.cc line 3466
  847 --Thread 139949722711808 has waited at btr0cur.cc line 554 for 77.00 seconds the semaphore:
  848 S-lock on RW-latch at 0x7f4a60043da8 created in file dict0dict.cc line 2341
  849 a writer (thread id 139957495039744) has reserved it in mode  wait exclusive
  850 number of readers 2, waiters flag 1, lock_word: fffffffffffffffe                                                        
  851 Last time read locked in file btr0cur.cc line 554
  852 Last time write locked in file /root/mysql-5.6.10/storage/innobase/btr/btr0cur.cc line 545
  853 --Thread 139945323890432 has waited at btr0cur.cc line 554 for 77.00 seconds the semaphore:
  854 S-lock on RW-latch at 0x7f4a60043da8 created in file dict0dict.cc line 2341
  855 a writer (thread id 139957495039744) has reserved it in mode  wait exclusive
  856 number of readers 2, waiters flag 1, lock_word: fffffffffffffffe

  857 Last time read locked in file btr0cur.cc line 554




本文转自 liqius 51CTO博客,原文链接:http://blog.51cto.com/szgb17/1919482,如需转载请自行联系原作者

2025-06-19 12:25:09 7716 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_wcs/baglifeinfo uses space ID: 2 at filepath: .\db_wcs\baglifeinfo.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd InnoDB: We do not continue the crash recovery, because the table may become InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it. InnoDB: To fix the problem and start mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot InnoDB: open the file, you should modify the permissions. InnoDB: 2) If the table is not needed, or you can restore it from a backup, InnoDB: then you can remove the .ibd file, and InnoDB will do a normal InnoDB: crash recovery and ignore that table. InnoDB: 3) If the file system or the disk is broken, and you cannot remove InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf InnoDB: and force InnoDB to continue crash recovery here. 2025-06-19 12:25:10 9448 [Note] Plugin 'FEDERATED' is disabled. 2025-06-19 12:25:10 224c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2025-06-19 12:25:10 9448 [Note] InnoDB: Using atomics to ref count buffer pool pages 2025-06-19 12:25:10 9448 [Note] InnoDB: The InnoDB memory heap is disabled 2025-06-19 12:25:10 9448 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-06-19 12:25:10 9448 [Note] InnoDB: Memory barrier is not used 2025-06-19 12:25:10 9448 [Note] InnoDB: Compressed tables use zlib 1.2.3 2025-06-19 12:25:10 9448 [Note] InnoDB: Not using CPU crc32 instructions 2025-06-19 12:25:10 9448 [Note] InnoDB: Initializing buffer pool, size = 8.0G 2025-06-19 12:25:10 9448 [Note] InnoDB: Completed initialization of buffer pool 2025-06-19 12:25:10 9448 [Note] InnoDB: Highest supported file format is Barracuda. 2025-06-19 12:25:10 9448 [Note] InnoDB: Log scan progressed past the checkpoint lsn 31950847983 2025-06-19 12:25:10 9448 [Note] InnoDB: Database was not shutdown normally! 2025-06-19 12:25:10 9448 [Note] InnoDB: Starting crash recovery. 2025-06-19 12:25:10 9448 [Note] InnoDB: Reading tablespace information from the .ibd files... 2025-06-19 12:25:10 9448 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_wcs/baglifeinfo uses space ID: 2 at filepath: .\db_wcs\baglifeinfo.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd InnoDB: We do not continue the crash recovery, because the table may become InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it. InnoDB: To fix the problem and start mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot InnoDB: open the file, you should modify the permissions. InnoDB: 2) If the table is not needed, or you can restore it from a backup, InnoDB: then you can remove the .ibd file, and InnoDB will do a normal InnoDB: crash recovery and ignore that table. InnoDB: 3) If the file system or the disk is broken, and you cannot remove InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf InnoDB: and force InnoDB to continue crash recovery here. 2025-06-19 12:25:12 7396 [Note] Plugin 'FEDERATED' is disabled. 2025-06-19 12:25:12 2484 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2025-06-19 12:25:12 7396 [Note] InnoDB: Using atomics to ref count buffer pool pages 2025-06-19 12:25:12 7396 [Note] InnoDB: The InnoDB memory heap is disabled 2025-06-19 12:25:12 7396 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-06-19 12:25:12 7396 [Note] InnoDB: Memory barrier is not used 2025-06-19 12:25:12 7396 [Note] InnoDB: Compressed tables use zlib 1.2.3 2025-06-19 12:25:12 7396 [Note] InnoDB: Not using CPU crc32 instructions 2025-06-19 12:25:12 7396 [Note] InnoDB: Initializing buffer pool, size = 8.0G 2025-06-19 12:25:12 7396 [Note] InnoDB: Completed initialization of buffer pool 2025-06-19 12:25:12 7396 [Note] InnoDB: Highest supported file format is Barracuda. 2025-06-19 12:25:12 7396 [Note] InnoDB: Log scan progressed past the checkpoint lsn 31950847983 2025-06-19 12:25:12 7396 [Note] InnoDB: Database was not shutdown normally! 2025-06-19 12:25:12 7396 [Note] InnoDB: Starting crash recovery. 2025-06-19 12:25:12 7396 [Note] InnoDB: Reading tablespace information from the .ibd files... 2025-06-19 12:25:12 7396 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_wcs/baglifeinfo uses space ID: 2 at filepath: .\db_wcs\baglifeinfo.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd InnoDB: We do not continue the crash recovery, because the table may become InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it. InnoDB: To fix the problem and start mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot InnoDB: open the file, you should modify the permissions. InnoDB: 2) If the table is not needed, or you can restore it from a backup, InnoDB: then you can remove the .ibd file, and InnoDB will do a normal InnoDB: crash recovery and ignore that table. InnoDB: 3) If the file system or the disk is broken, and you cannot remove InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf InnoDB: and force InnoDB to continue crash recovery here. 2025-06-19 12:25:13 1704 [Note] Plugin 'FEDERATED' is disabled. 2025-06-19 12:25:13 2d94 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 2025-06-19 12:25:13 1704 [Note] InnoDB: Using atomics to ref count buffer pool pages 2025-06-19 12:25:13 1704 [Note] InnoDB: The InnoDB memory heap is disabled 2025-06-19 12:25:13 1704 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-06-19 12:25:13 1704 [Note] InnoDB: Memory barrier is not used 2025-06-19 12:25:13 1704 [Note] InnoDB: Compressed tables use zlib 1.2.3 2025-06-19 12:25:13 1704 [Note] InnoDB: Not using CPU crc32 instructions 2025-06-19 12:25:13 1704 [Note] InnoDB: Initializing buffer pool, size = 8.0G 2025-06-19 12:25:13 1704 [Note] InnoDB: Completed initialization of buffer pool 2025-06-19 12:25:13 1704 [Note] InnoDB: Highest supported file format is Barracuda. 2025-06-19 12:25:13 1704 [Note] InnoDB: Log scan progressed past the checkpoint lsn 31950847983 2025-06-19 12:25:13 1704 [Note] InnoDB: Database was not shutdown normally! 2025-06-19 12:25:13 1704 [Note] InnoDB: Starting crash recovery. 2025-06-19 12:25:13 1704 [Note] InnoDB: Reading tablespace information from the .ibd files... 2025-06-19 12:25:13 1704 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db_wcs/baglifeinfo uses space ID: 2 at filepath: .\db_wcs\baglifeinfo.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd InnoDB: We do not continue the crash recovery, because the table may become InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it. InnoDB: To fix the problem and start mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot InnoDB: open the file, you should modify the permissions. InnoDB: 2) If the table is not needed, or you can restore it from a backup, InnoDB: then you can remove the .ibd file, and InnoDB will do a normal InnoDB: crash recovery and ignore that table. InnoDB: 3) If the file system or the disk is broken, and you cannot remove InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf InnoDB: and force InnoDB to continue crash recovery here. 这是一开始的报错日志信息,请帮忙分析报错1067的原因
最新发布
06-20
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值