Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.2.4
-
None
-
OS : Linux ubuntu16 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
bison :(GNU Bison) 3.0.4
gcc : version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
GNU Make: 4.1 (Built for x86_64-pc-linux-gnu)
cmake : version 3.5.1
libncurses : 6.0+20160213-1ubuntu1
libevent-dev: 2.0.21-stable-2ubuntu0.16.04.1
gnutls-cli : 3.4.10
YaSSL : 2.4.2
OpenSSL : 1.0.2g 1 Mar 2016OS : Linux ubuntu16 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux bison :(GNU Bison) 3.0.4 gcc : version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) GNU Make: 4.1 (Built for x86_64-pc-linux-gnu) cmake : version 3.5.1 libncurses : 6.0+20160213-1ubuntu1 libevent-dev: 2.0.21-stable-2ubuntu0.16.04.1 gnutls-cli : 3.4.10 YaSSL : 2.4.2 OpenSSL : 1.0.2g 1 Mar 2016
Description
Steps:
Followed the below steps to check the invalid system parameters innodb_defragment_fill_factor! and innodb_defragment_fill_factor-. Both are invalid. Server startup ABORTS as expected for innodb_defragment_fill_factor! but not for innodb_defragment_fill_factor-
- Downloaded the source from https://downloads.mariadb.org/interstitial/mariadb-10.2.4/source/mariadb-10.2.4.tar.gz
- Compile and Install MariaDB10.2.4 debug build. Use the build script ./BUILD/compile-pentium64-debug-max
- Change directory to 'mariadb-10.2.4/sql' folder. Run the following commands, change the datadir and log-error parameters path matching to the current installation
- Execute the following command with invalid server system variable innodb_defragment_fill_factor!
./mysqld --innodb_defragment_fill_factor!=29 --datadir=/home/vmatcha/sw/mariadb-10.2.4/data/ --log-error=../data/vmatcha_ubuntu_mysqld_10.2.4-logerror_1.txt &
- Server startup aborts correctly with the following error about invalid server system variable:
[ERROR] ./mysqld: unknown variable 'innodb_defragment_fill_factor!=29'
Attached the log vmatcha_ubuntu_mysqld_10.2.4-logerror_1.txt
- Execute the following command with a different invalid server system variable innodb_defragment_fill_factor-
./mysqld --innodb_defragment_fill_factor-=29 --datadir=/home/vmatcha/sw/mariadb-10.2.4/data/ --log-error=../data/vmatcha_ubuntu_mysqld_10.2.4-logerror_2.txt &
Actual Result:
- For step 6, Server started successfully with the wrong system variable innodb_defragment_fill_factor-
- A different server variable innodb_defragment_fill_factor_n_recs got updated with value provided in the wrong command line system variable innodb_defragment_fill_factor-
MariaDB [(none)]> SHOW VARIABLES LIKE 'innodb_defragment_fill_factor%';
|
+--------------------------------------+----------+
|
| Variable_name | Value |
|
+--------------------------------------+----------+
|
| innodb_defragment_fill_factor | 0.900000 |
|
| innodb_defragment_fill_factor_n_recs | 29 |
|
+--------------------------------------+----------+
|
2 rows in set (0.00 sec)
|
 |
MariaDB [(none)]>
|
Attached the log vmatcha_ubuntu_mysqld_10.2.4-logerror_2.txt
Expected Result:
- For step 6, Server startup should have aborted with unknown variable error for innodb_defragment_fill_factor-
- Server should not update a different server variable innodb_defragment_fill_factor_n_recs when wrong server variable innodb_defragment_fill_factor- provided at command line