feature: mysqld_safe have more NUMACTL options
Bug #1291474 reported by
Kenny Gryp
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Triaged
|
Wishlist
|
Unassigned | |||
5.6 |
Triaged
|
Wishlist
|
Unassigned | |||
5.7 |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I have worked on a customer case where they want to run multiple MySQL instances and have decided to use specific CPU's for this.
This requires different numactl settings than 'numa_interleave' which currently do not work with mysqld_safe
Attached you can find a modified version that adds 2 options:
--numa-
--numa-
Maybe a more flexible way is to add numa_arguments, where you can specify a string with any numactl option?
tags: | added: contribution |
To post a comment you must log in.
The number and type of numa args is much more than this. Instead
of adding specifics, it would be better to add this as `numa_args` option
wherein people can specify whatever args they want passed to
numactl (there are lot more).