Details
-
Task
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
None
Description
EDIT: This MDEV is irrelevant as its possible to put these parameters on the [mysqld_safe] section of my.cnf.
–
If you want MariaDB to be started at init time with the --numa-interleave parameter (or any other useful parameter such as --malloc-lib) passed to mysqld_safe, you actually need to modify the init script line invoking mysqld_safe, for example on the Debian init script :
/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &
|
Would be replaced with :
/usr/bin/mysqld_safe --numa-interleave "${@:2}" > /dev/null 2>&1 &
|
It could be problematic in case you would want to upgrade the init script to a newer version and dont remember or have the knowledge of the modifications or if you use a packaged version of MariaDB and the init script had been modified, you will have to either keep you modified script while not having its latest version or manually report the modifications on the new one.
A "debian-oriented" solution would be to use a package config file such as /etc/default/mariadb-server where parameters such as :
DAEMON_OPTS="--numa-interleave --sometingelse=50"
|
Or :
NUMA_INTERLEAVING=yes
|
SOMETHINGELSE=50
|
This way, the specific parameters would be kept upon init script upgrade and easy to find/modify.
Another universal solution could be to put a variable at the beginning of the init script that would be easier to report manually on another init script and could be kept on package upgrade.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description | Using the default init script provided with Debian/Ubuntu, i need to modify the init script for it to start mysqld_safe the the --numa-interleave parameter, having an /etc/debian/{mysql,mariadb} config file with parameters for the init script would be a good thing as you could stick with the vanilla init script. | Using the default init script provided with Debian/Ubuntu, i need to modify the init script for it to start mysqld_safe the the --numa-interleave parameter, having an /etc/debian/mariadb-server config file with parameters for mysqld_safe would be a good thing as you could stick with the vanilla init script. |
| Description | Using the default init script provided with Debian/Ubuntu, i need to modify the init script for it to start mysqld_safe the the --numa-interleave parameter, having an /etc/debian/mariadb-server config file with parameters for mysqld_safe would be a good thing as you could stick with the vanilla init script. |
If you want MariaDB to be started at init time with the --numa-interleave parameter (or any other useful parameter such as --malloc-lib) passed to mysqld_safe, you actually need to modify the init script line invoking mysqld_safe, for example on the Debian init script : {noformat}/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &{noformat} Would be replaced with : {noformat}/usr/bin/mysqld_safe --numa-interleave "${@:2}" > /dev/null 2>&1 &{noformat} It could be problematic in case you would want to upgrade the init script to a newer version and dont remember or have the knowledge of the modifications or if you use a packaged version of MariaDB and the init script had been modified, you will have to either keep you modified script while not having its latest version or manually report the modifications on the new one. A "debian-oriented" solution would be to use a package config file such as /etc/default/mariadb-server where parameters such as : {noformat}DAEMON_OPTS="--numa-interleave --sometingelse=50"{noformat} Or : {noformat}NUMA_INTERLEAVING=yes SOMETHINGELSE=50{noformat} This way, the specific parameters would be kept upon init script upgrade and easy to find/modify. Another universal solution could be to put a variable at the beginning of the init script that would be easier to report manually on another init script and could be kept on package upgrade. |
| Labels | init mysqld_safe script | |
| Summary | Add the possibility to define default parameters passed to mysqld_safe on the init script on Debian systems | Add the possibility set default parameters passed to mysqld_safe on the init script |
| Fix Version/s | 5.5.36 [ 14600 ] |
| Fix Version/s | 5.5.37 [ 15000 ] | |
| Fix Version/s | 5.5.36 [ 14600 ] |
| Description |
If you want MariaDB to be started at init time with the --numa-interleave parameter (or any other useful parameter such as --malloc-lib) passed to mysqld_safe, you actually need to modify the init script line invoking mysqld_safe, for example on the Debian init script : {noformat}/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &{noformat} Would be replaced with : {noformat}/usr/bin/mysqld_safe --numa-interleave "${@:2}" > /dev/null 2>&1 &{noformat} It could be problematic in case you would want to upgrade the init script to a newer version and dont remember or have the knowledge of the modifications or if you use a packaged version of MariaDB and the init script had been modified, you will have to either keep you modified script while not having its latest version or manually report the modifications on the new one. A "debian-oriented" solution would be to use a package config file such as /etc/default/mariadb-server where parameters such as : {noformat}DAEMON_OPTS="--numa-interleave --sometingelse=50"{noformat} Or : {noformat}NUMA_INTERLEAVING=yes SOMETHINGELSE=50{noformat} This way, the specific parameters would be kept upon init script upgrade and easy to find/modify. Another universal solution could be to put a variable at the beginning of the init script that would be easier to report manually on another init script and could be kept on package upgrade. |
*EDIT: This MDEV is irrelevant as its possible to put these parameters on the \[mysqld_safe] section of my.cnf.* -- If you want MariaDB to be started at init time with the --numa-interleave parameter (or any other useful parameter such as --malloc-lib) passed to mysqld_safe, you actually need to modify the init script line invoking mysqld_safe, for example on the Debian init script : {noformat}/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &{noformat} Would be replaced with : {noformat}/usr/bin/mysqld_safe --numa-interleave "${@:2}" > /dev/null 2>&1 &{noformat} It could be problematic in case you would want to upgrade the init script to a newer version and dont remember or have the knowledge of the modifications or if you use a packaged version of MariaDB and the init script had been modified, you will have to either keep you modified script while not having its latest version or manually report the modifications on the new one. A "debian-oriented" solution would be to use a package config file such as /etc/default/mariadb-server where parameters such as : {noformat}DAEMON_OPTS="--numa-interleave --sometingelse=50"{noformat} Or : {noformat}NUMA_INTERLEAVING=yes SOMETHINGELSE=50{noformat} This way, the specific parameters would be kept upon init script upgrade and easy to find/modify. Another universal solution could be to put a variable at the beginning of the init script that would be easier to report manually on another init script and could be kept on package upgrade. |
| Resolution | Won't Fix [ 2 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | defaullt [ 32400 ] | MariaDB v2 [ 42929 ] |
| Workflow | MariaDB v2 [ 42929 ] | MariaDB v3 [ 61958 ] |
| Workflow | MariaDB v3 [ 61958 ] | MariaDB v4 [ 132246 ] |