Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Databases and Redis

MySQL or XAMPP will not start: unknown variable innodb_additional_mem_pool_size

Errorunknown variable 'innodb_additional_mem_pool_size=2M'

Short answer

innodb_additional_mem_pool_size was deprecated in MySQL 5.6 and removed in 5.7, together with innodb_use_sys_malloc. A config file carried over from an older install still sets it, and the server refuses to start on an option it does not know. Delete both lines from the file the server really reads.

  • Applies to MySQL 5.7, MySQL 8.4, Windows my.ini
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Search the option files your install reads for the removed variables, to see which file still sets them.

    findstr /S /I "innodb_additional_mem_pool_size innodb_use_sys_malloc" C:\xampp\mysql\bin\my.ini C:\my.ini C:\Windows\my.ini
  2. 2Match what you see, then jump to its fix

    1. 1unknown variable 'innodb_additional_mem_pool_size=...' right after a version upgrade or a copied configThe option was removed in MySQL 5.7Fix
    2. 2You removed the line from my.ini and the same error comes backA second option file still carries the lineFix

What does the error look like?

  • unknown variable 'innodb_additional_mem_pool_size=2M'
  • [ERROR] Aborting

Cause 1 of 2

The option was removed in MySQL 5.7

1Check

innodb_additional_mem_pool_size and innodb_use_sys_malloc were deprecated in 5.6.2 and removed in 5.7. They were a pair: the memory pool setting was unused whenever sys malloc was on, so both go.

findstr /S /I "innodb_additional_mem_pool_size innodb_use_sys_malloc" C:\xampp\mysql\bin\my.ini

2Fix

Delete both lines from the option file.

[mysqld]
# removed:
# innodb_additional_mem_pool_size=2M
# innodb_use_sys_malloc=ON

3Verify

Search again: nothing should print. Then start the server and read the error log.

findstr /S /I "innodb_additional_mem_pool_size" C:\xampp\mysql\bin\my.ini

Confirmed by dev.mysql.com

Did this fix it?

Cause 2 of 2

A second option file still carries the line

1Check

The server reads several option files in a fixed order, and later ones win. On Windows these include the Windows directory, C:\, and the base directory of the install, so an old copy can sit in a place you did not edit.

dir /S /B C:\my.ini C:\my.cnf C:\Windows\my.ini C:\xampp\mysql\my.ini

2Fix

Remove the variable from every file that sets it, or rename the stray old copy.

rem edit each file found above, then search again
findstr /S /I "innodb_additional_mem_pool_size" C:\my.ini C:\Windows\my.ini

3Verify

No file prints a match any more.

findstr /S /I "innodb_use_sys_malloc" C:\my.ini C:\Windows\my.ini

Confirmed by dev.mysql.com

Did this fix it?

How do I stop it coming back?

  • When you upgrade a major version, start from the new default config and add your own settings back one by one.
  • Read the removed-feature list in the release notes before copying an old my.ini.
  • Search the option files for removed variables after every upgrade.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.