InnoDB does not start automatically with shm buffer pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Unassigned |
Bug Description
If we use buffer pool in shm, InnoDB can't start automatically after crash
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Warning: The innodb_
InnoDB: Do not change the following between restarts of the server while this option is being used:
InnoDB: * the mysqld executable between restarts of the server.
InnoDB: * the value of innodb_
InnoDB: * the value of innodb_page_size.
InnoDB: * datafiles created by InnoDB during this session.
InnoDB: Otherwise, data corruption in datafiles may result.
InnoDB: The shared memory segment containing the buffer pool is: key 0x1561 (5473).
InnoDB: A shared memory segment containing the buffer pool seems to already exist.
InnoDB: The existent shared memory segment is used.
InnoDB: Error: The shared memory was not shut down cleanly.
InnoDB: Fatal error: cannot allocate the memory for the buffer pool
100926 15:41:38 [ERROR] Plugin 'InnoDB' init function returned error.
100926 15:41:38 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
100926 15:41:38 [Note] /usr/local/
This is serious problem, as many production system are expect to restart mysqld automatically.
If needed we should remove and create segment from InnoDB.
Related branches
- Vadim Tkachenko: Approve
- Fred Linhoss (community): Approve (documentation)
-
Diff: 291 lines (+77/-39)1 file modifiedinnodb_buffer_pool_shm.patch (+77/-39)
Changed in percona-server: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Yasufumi Kinoshita (yasufumi-kinoshita) |
Changed in percona-server: | |
status: | Confirmed → Fix Committed |
Changed in percona-server: | |
status: | Fix Committed → Fix Released |
Please give me exact specification to obey.
This is alpha-version without no specification about exceptions.
"If needed we should remove and create segment from InnoDB."
is dull to be programmed.
Even if the segment does not seem to be buffer pool?
If the segment of the key is already used and cannot treat?
If the segment is used by another binary of mysqld?
and so on....
Please give me all pattern of shm usage.
There should be the case which should/can not restart automatically.