Bug #83044 Innodb: innodb_numa_interleave=1, use numa numa_get_mems_allowed (contribution)
Submitted: 19 Sep 2016 22:57 Modified: 28 Sep 2020 14:07
Reporter: OCA Admin (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[19 Sep 2016 22:57] OCA Admin 
Description:
This bug tracks a contribution by Daniel Black (Github user: grooverdan) as described in http://github.com/mysql/mysql-server/pull/104

How to repeat:
See description

Suggested fix:
See contribution code attached
[19 Sep 2016 22:57] OCA Admin 
Contribution submitted via Github - Innodb: innodb_numa_interleave=1, use numa numa_get_mems_allowed 
(*) Contribution by Daniel Black (Github grooverdan, mysql-server/pull/104#issuecomment-247898531): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: git_patch_85730684.txt (text/plain), 1.80 KiB.
[20 Sep 2016 5:52] MySQL Verification Team 
Hello Daniel,

Thank you for the report and contribution.

Thanks,
Umesh
[25 Jun 2020 4:26] Annamalai Gurusami 
Posted by developer:
 
This patch is applicable to mysql-8.0 as well.
[28 Sep 2020 14:07] Daniel Price 
Posted by developer:
 
Fixed as of the upcoming 5.7.33, 8.0.23 release, and here's the proposed changelog entry from the documentation team:

Calls to numa_all_nodes_ptr were replaced by the numa_get_mems_allowed()
function.