1. 程式人生 > >Mysql在高併發下的崩潰

Mysql在高併發下的崩潰

181017 16:47:17  InnoDB: Operating system error number 995 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html InnoDB: File name .\ibdata1 InnoDB: File operation call: 'Windows aio'. InnoDB: Cannot continue operation. 181017 17:23:19  InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 181017 17:23:19  InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 2363557447. InnoDB: Doing recovery: scanned up to log sequence number 0 2363610608 181017 17:23:19  InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99  InnoDB: Apply batch completed 181017 17:23:20  InnoDB: Started; log sequence number 0 2363610608 181017 17:23:20 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections. Version: '5.0.37-community-nt'  socket: ''  port: 3306  MySQL Community Edition (GPL) 181017 17:24:19  InnoDB: Error: trying to declare trx to enter InnoDB, but InnoDB: it already is declared.  

2018-10-22問題猜想:(準備實際測試)

經過網上檢索得知,很多都指向了innodb_thread_concurrency的併發控制!

innodb_thread_concurrency的取值範圍:0-1000,0標誌無限制,常規為CPU數*2