Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Not a Bug
-
Affects Version/s: 10.0.8
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Ubuntu 12.04 1GB RAM
Description
If I tried to set innodb_buffer_pool_size even as large as 384M I was unable to start the mysqld.
Unfortunately, I did not save the message from mariadb-error.log before I removed 10.0 and switched to 5.5.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
The value itself works fine in 10.0, it's not even big on the today's standards.
innodb_buffer_pool_size=384M:
MariaDB [test]> select @@innodb_buffer_pool_size;
---------------------------
---------------------------
---------------------------
1 row in set (0.00 sec)
MariaDB [test]> select @@version;
----------------------
----------------------
----------------------
1 row in set (0.00 sec)
innodb_buffer_pool_size=1G:
MariaDB [test]> select @@innodb_buffer_pool_size;
---------------------------
---------------------------
---------------------------
1 row in set (0.00 sec)
MariaDB [test]> select @@version;
----------------------
----------------------
----------------------
1 row in set (0.00 sec)
Considering that your machine has 1Gb RAM, it is not surprising that you couldn't set the value. Some default values got increased comparing to 5.5, so the most likely reason was that you just did not have enough memory to run it this way. If innodb_buffer_pool_size is important for you, you need to reduce some other values.