feature: mysqld_safe have more NUMACTL options

Bug #1291474 reported by Kenny Gryp
6
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-memory-prefer-node=NODE Set numactl --preferred=NODE
 --numa-cpu-node=NODE Set numactl --cpunodebind=NODE

Maybe a more flexible way is to add numa_arguments, where you can specify a string with any numactl option?

Tags: contribution
Revision history for this message
Kenny Gryp (gryp) wrote :
description: updated
tags: added: contribution
Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

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).

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-2444

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.