"InnoDB: Failed to set NUMA memory policy" on 32-bit hosts
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Low
|
Laurynas Biveinis | |||
5.7 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
PS 5.6 trunk:
sys_vars.
Test ended at 2016-08-22 08:52:08
line
2016-08-22 15:52:07 30010 [Warning] InnoDB: Failed to set NUMA memory policy to MPOL_INTERLEAVE (error: Function not implemented).
2016-08-22 15:52:07 30010 [Warning] InnoDB: Failed to set NUMA memory policy of buffer pool page frames to MPOL_INTERLEAVE (error: Function not implemented).
2016-08-22 15:52:07 30010 [Warning] InnoDB: Failed to set NUMA memory policy to MPOL_DEFAULT (error: Function not implemented).
^ Found warnings in /mnt/workspace/
ok
It looks like NUMA calls on 32-bit hosts return ENOSYS. Probably the CMake check should be made aware of this and not compile in NUMA support on such system.
OTOH, that's too much of a requirement for a build system. Suppressing the warning is enough.