innodb_log_block_size is not dynamic

Bug #1054090 reported by Jay Janssen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Medium
Hrvoje Matijakovic
5.1
Fix Released
Medium
Hrvoje Matijakovic
5.5
Fix Released
Medium
Hrvoje Matijakovic

Bug Description

http://www.percona.com/doc/percona-server/5.5/scalability/innodb_io_55.html#innodb_log_block_size

states the variable is 'dynamic, but it clearly is not:

mysql> set global innodb_log_block_size=4096;
ERROR 1238 (HY000): Variable 'innodb_log_block_size' is a read only variable

Also, does this either break backwards compatibility or require a fresh set logs? If so, it should be documented as such

Related branches

Revision history for this message
Ovais Tariq (ovais-tariq) wrote :
Download full text (11.7 KiB)

A fresh pair of logs is needed for the variable 'innodb_log_block_size' to be changed, which means a clean restart and removal of the old logs.

Here is how I tested it:

[root@ovaistariq-net mysql-test]# ./mtr --start-and-exit
Logging: ./mtr --start-and-exit
120922 13:38:24 [Note] Flashcache bypass: disabled
120922 13:38:24 [Note] Flashcache setup error is : ioctl failed

120922 13:38:24 [Note] Plugin 'FEDERATED' is disabled.
MySQL Version 5.5.23
Checking supported features...
 - skipping ndbcluster
 - SSL connections supported
Using suites: main,sys_vars,binlog,federated,rpl,innodb,perfschema
Collecting tests...
vardir: /work/sources/percona-server/5.5.23-25.3/Percona-Server/mysql-test/var
Removing old var directory...
Creating var directory '/work/sources/percona-server/5.5.23-25.3/Percona-Server/mysql-test/var'...
Installing system database...
Using server port 59141

==============================================================================

TEST RESULT TIME (ms) or COMMENT
--------------------------------------------------------------------------

worker[1] - 'localhost:13000' was not free
worker[1] Using MTR_BUILD_THREAD 301, with reserved ports 13010..13019
worker[1] mysql-test-run: WARNING: running this script as _root_ will cause some tests to be skipped
worker[1]
Started [mysqld.1 - pid: 10340, winpid: 10340]
worker[1] Using config for test main.1st
worker[1] Port and socket path for server(s):
worker[1] mysqld.1 13010 /work/sources/percona-server/5.5.23-25.3/Percona-Server/mysql-test/var/tmp/mysqld.1.sock
worker[1] Server(s) started, not waiting for them to finish

[root@ovaistariq-net mysql-test]# ../client/mysql -S ./var/tmp/mysqld.1.sock
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.5.23-rel25.3-log Percona Server with XtraDB (GPL), Release rel25.3, Revision 240

Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> select @@innodb_log_block_size;
+-------------------------+
| @@innodb_log_block_size |
+-------------------------+
| 512 |
+-------------------------+
1 row in set (0.00 sec)

mysql> set global innodb_log_block_size=4*1024;
ERROR 1238 (HY000): Variable 'innodb_log_block_size' is a read only variable
mysql> Bye

[root@ovaistariq-net mysql-test]# vim ./var/my.cnf
innodb_log_block_size=4096

[root@ovaistariq-net mysql-test]# ../client/mysqladmin -S ./var/tmp/mysqld.1.sock shutdown
120922 13:58:31 [Note] /work/sources/percona-server/5.5.23-25.3/Percona-Server/sql/mysqld: Normal shutdown

120922 13:58:31 [Note] Event Scheduler: Purging the queue. 0 events
120922 13:58:32 InnoDB: Starting shutdown...
120922 13:58:35 InnoDB: Shutdown completed; log sequence number 12599894
120922 13:58:35 [Note] /work/sources/percona-server/5.5.23-25.3/Percona-Server/sql/mysqld: Shutdown complete

[root@ovaistariq-net mysql-test]# /work/sources/percona-server/5.5.2...

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1271

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.