Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
There was a good fix in 5.5 that disabled Linux Native AIO in case of a problem, instead of making the server crash on startup:
revno: 3460
|
revision-id: monty@askmonty.org-20120627141312-z65pj80390f0f5pp
|
parent: wlad@montyprogram.com-20120625161724-05sguk5snhzdezzg
|
committer: Michael Widenius <monty@askmonty.org>
|
branch nick: maria-5.5
|
timestamp: Wed 2012-06-27 17:13:12 +0300
|
message:
|
Don't abort InnoDB/XtraDB if one can't allocate resources for AIO
|
- Better error messages
|
|
This fixes that one again can run the test systems with many threads without having to increase fs.aio-max-nr.
|
In current 10.0 the fix for XtraDB (which is basically 5.5) is still present, but for InnoDB it disappeared, apparently after the previous merge.
Please add it back when the next merge is finished.
130605 0:49:26 InnoDB: Compressed tables use zlib 1.2.3.4
|
130605 0:49:26 InnoDB: Using Linux native AIO
|
130605 0:49:26 InnoDB: CPU does not support crc32 instructions
|
130605 0:49:27 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
|
InnoDB: Warning: io_setup() attempt 1 failed.
|
InnoDB: Warning: io_setup() attempt 2 failed.
|
InnoDB: Warning: io_setup() attempt 3 failed.
|
InnoDB: Warning: io_setup() attempt 4 failed.
|
InnoDB: Warning: io_setup() attempt 5 failed.
|
130605 0:49:29 InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
|
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
|
130605 0:49:29 InnoDB: Initializing buffer pool, size = 128.0M
|
130605 0:49:29 InnoDB: Completed initialization of buffer pool
|
130605 0:49:29 [ERROR] mysqld got signal 11 ;
|
bzr version-info
|
revision-id: wlad@montyprogram.com-20130523125248-22m56m01r24t0dmb
|
revno: 3752
|
branch-nick: 10.0
|
Attachments
Issue Links
- relates to
-
-
- Closed
-