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

本文涉及的产品
云数据库 RDS MySQL,集群系列 2核4GB
推荐场景:
搭建个人博客
RDS MySQL Serverless 基础系列,0.5-2RCU 50GB
RDS MySQL Serverless 高可用系列,价值2615元额度,1个月
简介:

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,如需转载请自行联系原作者

相关实践学习
如何快速连接云数据库RDS MySQL
本场景介绍如何通过阿里云数据管理服务DMS快速连接云数据库RDS MySQL,然后进行数据表的CRUD操作。
全面了解阿里云能为你做什么
阿里云在全球各地部署高效节能的绿色数据中心,利用清洁计算为万物互联的新世界提供源源不断的能源动力,目前开服的区域包括中国(华北、华东、华南、香港)、新加坡、美国(美东、美西)、欧洲、中东、澳大利亚、日本。目前阿里云的产品涵盖弹性计算、数据库、存储与CDN、分析与搜索、云通信、网络、管理与监控、应用服务、互联网中间件、移动服务、视频服务等。通过本课程,来了解阿里云能够为你的业务带来哪些帮助     相关的阿里云产品:云服务器ECS 云服务器 ECS(Elastic Compute Service)是一种弹性可伸缩的计算服务,助您降低 IT 成本,提升运维效率,使您更专注于核心业务创新。产品详情: https://www.aliyun.com/product/ecs
相关文章
|
关系型数据库 MySQL Java
【MySQL异常解决】Operation not allowed when innodb_forced_recovery > 0 的解决办法
【MySQL异常解决】Operation not allowed when innodb_forced_recovery > 0 的解决办法
334 0
【MySQL异常解决】Operation not allowed when innodb_forced_recovery > 0 的解决办法
|
7月前
|
Java
Intellij IDEA运行报Command line is too long的解决办法
Intellij IDEA运行报Command line is too long的解决办法
489 1
针对报错:java.lang.Integer cannot be cast to java.lang.Long..的解决办法
针对报错:java.lang.Integer cannot be cast to java.lang.Long..的解决办法
4360 0
针对报错:java.lang.Integer cannot be cast to java.lang.Long..的解决办法
|
SQL 关系型数据库 MySQL
MySQL因为hung住,自动重新启动,InnoDB: Semaphore wait has lasted > 600 seconds
从错误日志中检查,有两个信号量等待时间超长,MySQL自动crash了
468 0
IDEA运行报Command line is too long错误解决办法
IDEA运行报Command line is too long错误解决办法
552 0
IDEA运行报Command line is too long错误解决办法
|
关系型数据库 MySQL 数据库
MySQL错误“Specified key was too long; max key length is 1000 bytes”的解决办法
MySQL错误“Specified key was too long; max key length is 1000 bytes”的解决办法 经过查询才知道,是Mysql的字段设置的太长了,于是我把这两个字段的长度改了一下就好了。
1867 0
Unicode下TRACE中文(_CrtDbgReport: String too long or IO Error) .解决办法
Unicode下TRACE中文(_CrtDbgReport: String too long or IO Error)        在使用Unicode的工程项目中,如果是Debug模式。当TRACE Unicode字符串时,会输出提示:_CrtDbgReport: String too lon...
1205 0
|
7月前
|
JSON JavaScript 前端开发
解决js中Long类型数据在请求与响应过程精度丢失问题(springboot项目中)
解决js中Long类型数据在请求与响应过程精度丢失问题(springboot项目中)
654 0